Searched full:situation (Results 1 – 25 of 672) sorted by relevance
12345678910>>...27
| /Linux-v5.10/Documentation/RCU/ |
| D | arrayRCU.rst | 31 Situation 1: Hash Tables
41 Situation 2: Static Arrays
47 this situation, which would also have minimal read-side overhead as long
57 Situation 3: Resizable Arrays
|
| D | rcubarrier.rst | 187 Is there any other situation where rcu_barrier() might
302 Is there any other situation where rcu_barrier() might
307 RCU in a filesystem, which resulted in a similar situation at
|
| D | checklist.rst | 14 0. Is RCU being applied to a read-mostly situation? If the data
23 provides a simpler implementation. An example of this situation
33 counter-intuitive situation where rcu_read_lock() and
83 of ways to handle this concurrency, depending on the situation:
|
| /Linux-v5.10/drivers/staging/unisys/Documentation/ABI/ |
| D | sysfs-platform-visorchipset | 64 situation by sending a message to guests using these VFs, and
83 situation by sending a message to guests using these VFs, and
|
| /Linux-v5.10/Documentation/timers/ |
| D | timers-howto.rst | 70 will obviously depend on your specific situation, but
100 tolerances here are very situation specific, thus it
|
| /Linux-v5.10/lib/ |
| D | Kconfig.kgdb | 141 kernel is still usable in this situation.
143 No guarantees that the kernel is still usable in this situation.
|
| /Linux-v5.10/Documentation/process/ |
| D | volatile-considered-harmful.rst | 61 Another situation where one might be tempted to use volatile is
96 type of situation.
|
| D | 3.Early-stage.rst | 51 The reality of the situation was different; the kernel developers were far
187 idea. The best thing to do in this situation is to proceed, keeping the
216 designed to help with this sort of situation; more information can be found
|
| /Linux-v5.10/drivers/usb/serial/ |
| D | aircable.c | 22 * situation, when too much data arrives to the device because it sends the data
23 * but with out the header. I will use a simply hack to override this situation,
|
| /Linux-v5.10/drivers/rapidio/switches/ |
| D | idt_gen3.c | 220 * If the link is up (PORT_OK) - situation is handled as *new* device insertion.
226 * TODO: This is not sufficient in a situation when a link between two devices
227 * was down and up again (e.g. cable disconnect). For that situation full ackID
|
| /Linux-v5.10/Documentation/admin-guide/aoe/ |
| D | todo.rst | 8 free page is needed for the sk_buff allocation. This situation has
|
| /Linux-v5.10/drivers/bcma/ |
| D | README | 17 In this situation we decided to introduce separated bus. It can contain up to
|
| /Linux-v5.10/drivers/accessibility/speakup/ |
| D | TODO | 13 has been able to find a situation which produces it consistently.
|
| /Linux-v5.10/Documentation/devicetree/bindings/iio/multiplexer/ |
| D | io-channel-mux.txt | 4 e.g. an ADC channel, these bindings describe that situation.
|
| /Linux-v5.10/Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 7 Situation:
17 Another situation is when the silicon temperature continues to
|
| /Linux-v5.10/arch/sparc/include/asm/ |
| D | machines.h | 39 * SM_SUN4M_OBP then you have the following situation:
|
| /Linux-v5.10/Documentation/devicetree/bindings/ |
| D | ABI.rst | 41 devicetree maintainers overrules this document. In that situation, a patch
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-driver-typec-displayport | 20 USB Type-C Standard. Functionally it equals to the situation
|
| D | sysfs-devices-platform-ipmi | 168 disables interrupts when it gets into a situation where it
170 situation clears up, it will re-enable interrupts.
|
| /Linux-v5.10/Documentation/admin-guide/device-mapper/ |
| D | snapshot.rst | 108 we'll have this situation (with volumes in above order)::
138 we'll now have this situation::
|
| D | dm-integrity.rst | 17 situation the dm-crypt target creates the integrity data and passes them
153 situation, you can encrypt the journal.
|
| /Linux-v5.10/Documentation/devicetree/bindings/regulator/ |
| D | vctrl.txt | 25 avoid this situation the vctrl driver breaks down
|
| /Linux-v5.10/Documentation/devicetree/bindings/bus/ |
| D | baikal,bt1-axi.yaml | 21 an IRQ is raised and a faulty situation is reported to the AXI EHB
|
| /Linux-v5.10/tools/testing/selftests/ftrace/ |
| D | README | 62 The test which is in above situation, must call exit_unresolved.
|
| /Linux-v5.10/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 186 This is the most common situation and it is quite straightforward: we want
274 situation described below:
|
12345678910>>...27
