Searched full:situations (Results 1 – 25 of 129) sorted by relevance
123456
| /Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 68 situations where we want to avoid one device taking all or
81 of 1 million. This is useful in situations where we want to avoid
109 situations where we want to avoid one device taking all or
122 is useful in situations where the global limit is much higher than
|
| D | sysfs-fs-erofs | 18 - 2 (force off): disable for all situations.
|
| D | sysfs-devices-real_power_state | 17 In some situations the value of this attribute may be different
|
| D | sysfs-bus-iio-trigger-sysfs | 9 automated testing or in situations, where other trigger methods
|
| /Documentation/timers/ |
| D | no_hz.rst | 38 there are some situations where this old-school approach is still the
84 unnecessary scheduling-clock interrupts. In these situations, there
121 by one less than the number of CPUs. In these situations, there is
180 There are situations in which idle CPUs cannot be permitted to
258 of other situations where the scheduling-clock tick is not
275 Better handling of these sorts of situations is future work.
|
| /Documentation/locking/ |
| D | preempt-locking.rst | 15 requires explicit additional locking for very few additional situations.
18 requires protecting these situations.
35 protect these situations by disabling preemption around them.
|
| /Documentation/admin-guide/ |
| D | edid.rst | 24 As a remedy for such situations, the kernel configuration item
|
| D | cpu-load.rst | 51 One can imagine many more situations where this behavior of the kernel
|
| /Documentation/devicetree/bindings/regulator/ |
| D | qcom,usb-vbus-regulator.yaml | 14 regulator will be enabled in situations where the device is required to
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | qcom,sec-qfprom.yaml | 14 protected from non-secure access. In such situations, the OS have to use
|
| /Documentation/networking/device_drivers/can/freescale/ |
| D | flexcan.rst | 25 performs better under high system load situations.
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 111 the mainline. The best practices to follow differ in those two situations.
190 as always, in such situations, the merge commit should explain why the
219 be situations that call out for a different solution, and these guidelines
|
| /Documentation/i2c/ |
| D | gpio-fault-injection.rst | 46 The following fault injectors create situations where SDA will be held low by a
47 device. Bus recovery should be able to fix these situations. But please note:
|
| /Documentation/mm/ |
| D | overcommit-accounting.rst | 23 use, in most situations this means a process will not be
|
| /Documentation/arch/arm/ |
| D | vlocks.rst | 10 which are otherwise non-coherent, in situations where the hardware
89 vlocks are therefore best suited to situations where it is necessary
|
| /Documentation/driver-api/iio/ |
| D | triggers.rst | 12 In many situations it is useful for a driver to be able to capture data based
|
| /Documentation/fb/ |
| D | tridentfb.rst | 59 detection says in all three BIOS selectable situations 2M, 4M, 8M.
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-subscribe-event.rst | 106 situations like that.
|
| /Documentation/RCU/ |
| D | rcu.rst | 26 in read-mostly situations. The fact that RCU readers need not
|
| /Documentation/core-api/ |
| D | kref.rst | 148 know what you are doing (there are some situations where locking is
153 There are some situations where you can optimize the gets and puts.
|
| /Documentation/networking/ |
| D | tproxy.rst | 62 acceptable in certain situations. (Think of proxying UDP for example: you won't
|
| /Documentation/gpu/ |
| D | drm-vm-bind-async.rst | 84 In low-memory situations the implementation may block, performing the
153 In these situations UMD should preferably restart the IOCTL after
|
| /Documentation/admin-guide/mm/damon/ |
| D | lru_sort.rst | 20 situations including reclamation target pages selection under sudden memory
44 be widely used without harm for common situations while providing a level of
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | rdma.rst | 67 Resource pool object is created in following situations.
|
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 73 There are still a few rare situations where volatile makes sense in the
|
123456