Searched full:situation (Results 1 – 25 of 1470) sorted by relevance
12345678910>>...59
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-6.6/Documentation/timers/ |
| D | timers-howto.rst | 70 will obviously depend on your specific situation, but
100 tolerances here are very situation specific, thus it
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-6.6/Documentation/RCU/ |
| D | rcubarrier.rst | 54 This situation can be handled by the rcu_barrier() primitive. Rather
166 Is there any other situation where rcu_barrier() might
296 Is there any other situation where rcu_barrier() might
302 RCU in a filesystem, which resulted in a similar situation at
|
| /kernel/linux/linux-6.6/Documentation/tools/rtla/ |
| D | rtla-hwnoise.rst | 78 The tool should report *0* hardware-related noise in the ideal situation.
82 the ideal situation in the same hardware::
|
| /kernel/linux/linux-6.6/lib/ |
| D | Kconfig.kgdb | 141 kernel is still usable in this situation.
143 No guarantees that the kernel is still usable in this situation.
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-5.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,
|
| /kernel/linux/linux-6.6/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
188 idea. The best thing to do in this situation is to proceed, keeping the
217 designed to help with this sort of situation; more information can be found
|
| /kernel/linux/linux-6.6/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,
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-6.6/include/linux/regulator/ |
| D | driver.h | 91 * current situation detection. Detection can be configured for three
96 * - REGULATOR_SEVERITY_ERR should indicate that over-current situation is
100 * - REGULATOR_SEVERITY_WARN should indicate situation where hardware is
107 * voltage situation detection. Detection can be configured for same
110 * under voltage situation detection. Detection can be configured for same
113 * temperature situation detection.Detection can be configured for same
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/aoe/ |
| D | todo.rst | 8 free page is needed for the sk_buff allocation. This situation has
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/aoe/ |
| D | todo.rst | 8 free page is needed for the sk_buff allocation. This situation has
|
| /kernel/linux/linux-6.6/tools/perf/util/ |
| D | sharded_mutex.h | 9 * In a situation where a lock is needed per object, having a mutex can be
|
| /kernel/linux/linux-5.10/drivers/bcma/ |
| D | README | 17 In this situation we decided to introduce separated bus. It can contain up to
|
| /kernel/linux/linux-6.6/drivers/bcma/ |
| D | README | 17 In this situation we decided to introduce separated bus. It can contain up to
|
| /kernel/linux/linux-6.6/drivers/accessibility/speakup/ |
| D | TODO | 13 has been able to find a situation which produces it consistently.
|
| /kernel/linux/linux-5.10/drivers/accessibility/speakup/ |
| D | TODO | 13 has been able to find a situation which produces it consistently.
|
12345678910>>...59