| /OK3568_Linux_fs/kernel/Documentation/RCU/ |
| H A 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
|
| H A 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
|
| H A 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:
|
| /OK3568_Linux_fs/kernel/drivers/staging/unisys/Documentation/ABI/ |
| H A 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
|
| /OK3568_Linux_fs/yocto/poky/documentation/sdk-manual/ |
| H A D | extensible.rst | 253 situation where the source code does not exist locally and needs
254 to be extracted. In this situation, the source code is extracted
268 situation where the source code does not exist locally. In this
292 - *Right*: The right scenario in the figure represents a situation
416 The typical situation is where another developer has created a layer
422 situation where the source code does not exist locally and it
423 needs to be extracted from an upstream source. In this situation,
458 - *Middle*: The middle scenario in the figure represents a situation
491 - *Right*: The right scenario in the figure represents a situation
637 A common situation is where third-party software has undergone a
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/timers/ |
| H A D | timers-howto.rst | 70 will obviously depend on your specific situation, but
100 tolerances here are very situation specific, thus it
|
| /OK3568_Linux_fs/kernel/drivers/rapidio/switches/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A 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
|
| H A D | volatile-considered-harmful.rst | 61 Another situation where one might be tempted to use volatile is
96 type of situation.
|
| /OK3568_Linux_fs/kernel/lib/ |
| H A D | Kconfig.kgdb | 141 kernel is still usable in this situation.
143 No guarantees that the kernel is still usable in this situation.
|
| /OK3568_Linux_fs/buildroot/dl/stressapptest/git/ |
| H A D | README.md | 3 …om processor and I/O, with the intent of creating a realistic high load situation in order to test…
59 …ffic to memory from processor and I/O, with the intent of creating a realistic high load situation.
|
| /OK3568_Linux_fs/kernel/drivers/usb/serial/ |
| H A 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,
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/container/ |
| H A D | vector.hpp | 2788 //Old situation:
2795 //New situation in Case A (hole_size == 0):
2807 //New situation in Case B (hole_size >= 0):
2818 //New situation in Case C (hole_size == 0):
3001 //Old situation: in priv_forward_range_insert_expand_backwards()
3006 //New situation: in priv_forward_range_insert_expand_backwards()
3026 //Old situation: in priv_forward_range_insert_expand_backwards()
3031 //New situation: in priv_forward_range_insert_expand_backwards()
3071 //Old situation: in priv_forward_range_insert_expand_backwards()
3076 //New situation with do_after: in priv_forward_range_insert_expand_backwards()
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/ref-manual/ |
| H A D | qa-checks.rst | 115 go into the ``-dev`` package. This situation might occur if you add
150 not appear in anything but the ``-dbg`` package. This situation might
227 sections. This situation can result in a performance impact at
249 for this situation is to pass in :term:`LDFLAGS` using
424 unrecognized. This situation could be because the options were
681 task. Patch fuzz is a situation when the ``patch`` tool ignores some of the context
|
| /OK3568_Linux_fs/buildroot/package/hans/ |
| H A D | Config.in | 10 This can be useful when you find yourself in the situation
|
| /OK3568_Linux_fs/buildroot/package/cppunit/ |
| H A D | Config.in | 4 # currently the static situation is not correctly detected.
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | customize-rootfs.txt | 28 such a situation, should the overlay have any programs or libraries,
117 In such a situation, should the skeleton have any programs or
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-benchmark/stressapptest/ |
| H A D | stressapptest_1.0.9.bb | 5 situation in order to test the existing hardware devices in a computer. \
|
| /OK3568_Linux_fs/buildroot/package/mbedtls/ |
| H A D | Config.in | 30 particular situation.
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/aoe/ |
| H A D | todo.rst | 8 free page is needed for the sk_buff allocation. This situation has
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/thermal/ |
| H A D | cpu-idle-cooling.rst | 7 Situation:
17 Another situation is when the silicon temperature continues to
|
| /OK3568_Linux_fs/buildroot/package/efivar/ |
| H A D | Config.in | 13 # and the efivar source handles that situation. However, some
|
| /OK3568_Linux_fs/kernel/drivers/bcma/ |
| H A D | README | 17 In this situation we decided to introduce separated bus. It can contain up to
|
| /OK3568_Linux_fs/u-boot/doc/device-tree-bindings/net/ |
| H A D | fixed-link.txt | 8 Such a fixed link situation is described by creating a 'fixed-link'
|
| /OK3568_Linux_fs/kernel/drivers/accessibility/speakup/ |
| H A D | TODO | 13 has been able to find a situation which produces it consistently.
|