| /linux/Documentation/RCU/ |
| A D | checklist.rst | 28 read-side primitives is critically important.
92 primitives to add, remove, and replace elements on
109 appear atomic, as will individual atomic primitives.
112 of multiple atomic primitives. One alternative is to
157 various "_rcu()" list-traversal primitives, such
161 primitives. This is particularly useful in code that
168 list-traversal primitives can substitute for a good
172 and list_add_rcu() primitives must be used in order
228 primitives such as call_rcu().
339 9. All RCU list-traversal primitives, which include
[all …]
|
| A D | lockdep.rst | 14 In addition, RCU provides the following primitives that check lockdep's
30 checking of rcu_dereference() primitives:
107 traversal primitives check for being called from within an RCU read-side
110 traversal primitives will complain only if the lockdep expression is
|
| A D | whatisRCU.rst | 186 This temporal primitives is used by a reader to inform the
273 the _rcu list-manipulation primitives such as list_add_rcu().
340 primitives, such as list_for_each_entry_rcu() [2]_.
399 synchronize_rcu() and call_rcu() primitives used are the same for all three
400 flavors. However for protection (on the reader side), the primitives used vary
429 their assorted primitives.
512 rcu_assign_pointer() primitives from interfering with each other.
635 in terms of familiar locking primitives, and another that more closely
651 familiar locking primitives. Its overhead makes it a non-starter for
1173 update primitives.
[all …]
|
| A D | rcu_dereference.rst | 8 returned from the rcu_dereference() family of primitives carry address and
27 - You must use one of the rcu_dereference() family of primitives
31 Without one of the rcu_dereference() primitives, compilers
177 kernel's wide array of primitives that cause code to
|
| A D | rcu.rst | 59 "synchronize_srcu", and the other RCU primitives. Or grab one
|
| A D | listRCU.rst | 146 primitives add READ_ONCE() and diagnostic checks for incorrect use
221 The list_del(), list_add(), and list_add_tail() primitives have been
223 The **_rcu()** list-manipulation primitives add memory barriers that are
|
| /linux/tools/memory-model/Documentation/ |
| A D | ordering.txt | 46 Note well that many of these primitives generate absolutely no code
58 The Linux-kernel primitives that provide full ordering include:
65 o RCU's grace-period primitives.
113 Finally, RCU's grace-period primitives provide full ordering. These
114 primitives include synchronize_rcu(), synchronize_rcu_expedited(),
117 Furthermore, RCU's grace-period primitives can only be invoked in
118 sleepable contexts. Therefore, RCU's grace-period primitives are
378 Compared to locking primitives and RMW atomic operations, markers
460 primitives required the compiler to emit the corresponding store
468 primitives required the compiler to emit the corresponding load
[all …]
|
| A D | simple.txt | 52 Please use the standard locking primitives provided by the kernel rather
53 than rolling your own. For one thing, the standard primitives interact
54 properly with lockdep. For another thing, these primitives have been
131 Packaged primitives: Sequence locking
148 primitives. (LKMM does not yet know about sequence locking, so it is
153 Packaged primitives: RCU
168 Packaged primitives: Atomic operations
194 Reading code using these primitives is often also quite helpful.
223 WRITE_ONCE() can safely be used in some cases. These primitives provide
226 One example use for these primitives is statistics, such as per-CPU
[all …]
|
| A D | README | 17 like an overview of the types of low-level concurrency primitives
22 o You are familiar with the Linux-kernel concurrency primitives
80 primitives in terms of events.
92 primitives by category.
|
| /linux/Documentation/devicetree/bindings/mailbox/ |
| A D | nvidia,tegra186-hsp.yaml | 16 primitives for interprocessor communication. So the interprocessor
18 primitives, when operating between two processors not in an SMP
|
| /linux/tools/testing/selftests/powerpc/ |
| A D | Makefile | 20 primitives \
|
| /linux/Documentation/core-api/ |
| A D | genericirq.rst | 121 primitives referenced by the assigned chip descriptor structure.
183 The helper functions call the chip primitives and are used by the
279 The simple flow handler does not call any handler/chip primitives.
367 These primitives are strictly intended to mean what they say: ack means
386 chip primitives. The per-irq structure is protected via desc->lock, by
|
| A D | index.rst | 64 Concurrency primitives
|
| /linux/drivers/firmware/arm_scmi/transports/ |
| A D | Kconfig | 63 primitives all over instead. If unsure say N.
121 primitives all over instead. If unsure say N.
|
| /linux/Documentation/locking/ |
| A D | locktypes.rst | 12 The kernel provides a variety of locking primitives which can be divided
34 versions of these primitives. In short, don't acquire sleeping locks from
59 preemption and interrupt disabling primitives. Contrary to other locking
165 interrupt disabling and enabling primitives:
177 primitives:
180 of the protection scope while the regular primitives are scopeless and
|
| /linux/Documentation/devicetree/bindings/firmware/ |
| A D | nvidia,tegra210-bpmp.txt | 16 - reg: physical base address and length for HW synchornization primitives
|
| /linux/tools/net/sunrpc/xdrgen/grammars/ |
| A D | xdr.lark | 103 // XDR language primitives
|
| /linux/include/linux/ |
| A D | intel_rapl.h | 85 u64 primitives[NR_RAPL_PRIMITIVES]; member
|
| /linux/Documentation/driver-api/usb/ |
| A D | dma.rst | 44 For those specific cases, USB has primitives to allocate less expensive
55 Most drivers should **NOT** be using these primitives; they don't need
|
| /linux/Documentation/ |
| A D | atomic_t.txt | 183 Fully ordered primitives are ordered against everything prior and everything
202 ordering on their SMP atomic primitives. For example our TSO architectures
367 their locking primitives.
|
| /linux/Documentation/process/ |
| A D | volatile-considered-harmful.rst | 21 Like volatile, the kernel primitives which make concurrent access to data
38 primitives act as memory barriers - they are explicitly written to do so -
|
| /linux/Documentation/driver-api/ |
| A D | i2c.rst | 35 operations, either using I2C primitives or by issuing SMBus commands to
|
| /linux/tools/testing/selftests/futex/ |
| A D | README | 11 primitives. These can be used as is in user applications or can serve as
|
| /linux/Documentation/staging/ |
| A D | speculation.rst | 73 primitives.
|
| /linux/drivers/crypto/caam/ |
| A D | Kconfig | 142 Supported cryptographic primitives: encryption, decryption,
|