Searched full:strategy (Results 1 – 25 of 30) sorted by relevance
12
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 22 is affected by the state changes, this strategy is referred to as the
25 The other strategy, referred to as the :doc:`working-state power management
28 this strategy is in use, the working state of the system usually does not
|
| D | cpuidle.rst | 194 the time sharing strategy of the CPU scheduler. Of course, if there are
348 for tickless systems. It follows the same basic strategy as the ``menu`` `one
|
| /Documentation/networking/ |
| D | ipvs-sysctl.txt | 14 enough available memory, the respective strategy will be
16 the strategy is disabled and the variable is set to 1.
106 that this strategy is always disabled, 1 and 2 mean automatic
107 modes (when there is no enough available memory, the strategy
109 otherwise the strategy is disabled and the variable is set to
110 1), and 3 means that that the strategy is always enabled.
|
| D | timestamping.txt | 300 different from deciding on a strategy for IP fragmentation. There, the
|
| /Documentation/firmware-guide/acpi/ |
| D | osi.rst | 98 That is the *only* viable strategy, as that is what modern Windows does,
127 This strategy is problematic, as Linux is never completely compatible with
143 The result is a strategy for Linux to maximize compatibility with
175 Like Linux's _OSI("*Windows*") strategy, Linux defaults to
178 Just like on Windows-tested platforms, this strategy has risks.
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 28 viable recovery strategy.
|
| /Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 23 drivers could add this as a strategy to avoid unnecessary operation for
|
| /Documentation/x86/ |
| D | mds.rst | 70 Mitigation strategy
73 All variants have the same mitigation strategy at least for the single CPU
|
| D | tsx_async_abort.rst | 21 Mitigation strategy
|
| D | pat.rst | 135 implementation defined, yet this strategy can be used as last resort on devices
|
| /Documentation/devicetree/bindings/riscv/ |
| D | cpus.yaml | 21 strategy. For example, an Intel laptop containing one socket with
|
| /Documentation/media/uapi/dvb/ |
| D | dvbproperty.rst | 23 In the past (up to DVB API version 3 - DVBv3), the strategy used was to have a
|
| /Documentation/filesystems/ |
| D | hpfs.txt | 271 Better anti-fragmentation strategy
287 Better allocation strategy
|
| D | erofs.txt | 59 cache_strategy=%s Select a strategy for cached decompression from now on:
|
| D | journalling.rst | 100 strategy. Why? Because, if you do a delete, you need to ensure you
|
| /Documentation/networking/device_drivers/toshiba/ |
| D | spider_net.txt | 178 As of this writing, the spider_net_resync() strategy seems to work very
|
| /Documentation/block/ |
| D | queue-sysfs.rst | 95 a device recovery strategy.
|
| /Documentation/ABI/testing/ |
| D | sysfs-block | 290 the request, to fail it or to start a device recovery strategy.
|
| D | sysfs-class-power | 392 Pixel C's thermal management strategy to effectively limit the
|
| /Documentation/networking/device_drivers/stmicro/ |
| D | stmmac.txt | 278 available. As strategy adopted in this driver, the information from the HW
|
| /Documentation/scsi/ |
| D | BusLogic.txt | 164 the bus device reset error recovery strategy is selected and sending a bus
|
| /Documentation/cdrom/ |
| D | cdrom-standard.rst | 719 The preferred strategy of *open()*
808 function becomes active. A strategy is implemented in this routine,
|
| /Documentation/admin-guide/laptops/ |
| D | laptop-mode.rst | 93 To increase the effectiveness of the laptop_mode strategy, the laptop_mode
|
| /Documentation/driver-api/gpio/ |
| D | legacy.rst | 72 optional code supporting such an implementation strategy, described later
|
| /Documentation/kernel-hacking/ |
| D | hacking.rst | 318 out-of-memory error-handling strategy.
|
12