Searched refs:primitives (Results 1 – 25 of 58) sorted by relevance
123
| /Linux-v5.10/Documentation/RCU/ |
| D | checklist.rst | 28 read-side primitives is critically important.
60 rcu_read_lock() and friends? These primitives are needed
86 primitives to add, remove, and replace elements on
103 appear atomic, as will individual atomic primitives.
106 of multiple atomic primitives.
149 various "_rcu()" list-traversal primitives, such
153 primitives. This is particularly useful in code that
160 list-traversal primitives can substitute for a good
164 and list_add_rcu() primitives must be used in order
176 The list_replace_rcu() and hlist_replace_rcu() primitives
[all …]
|
| D | lockdep.rst | 14 In addition, RCU provides the following primitives that check lockdep's
28 checking of rcu_dereference() primitives:
104 traversal primitives check for being called from within an RCU read-side
107 traversal primitives will complain only if the lockdep expression is
|
| D | rcu_dereference.rst | 7 the similar primitives without worries. Dereferencing (prefix "*"),
14 - You must use one of the rcu_dereference() family of primitives
18 Without one of the rcu_dereference() primitives, compilers
151 kernel's wide array of primitives that cause code to
|
| D | listRCU.rst | 123 become list_for_each_entry_rcu(). The **_rcu()** list-traversal primitives
197 The list_del(), list_add(), and list_add_tail() primitives have been
199 The **_rcu()** list-manipulation primitives add memory barriers that are needed on
|
| D | whatisRCU.rst | 245 the _rcu list-manipulation primitives such as list_add_rcu().
307 primitives, such as list_for_each_entry_rcu() [2]_.
363 synchronize_rcu() and call_rcu() primitives used are the same for all three
364 flavors. However for protection (on the reader side), the primitives used vary
475 rcu_assign_pointer() primitives from interfering with each other.
592 in terms of familiar locking primitives, and another that more closely
608 familiar locking primitives. Its overhead makes it a non-starter for
|
| D | rcu.rst | 60 "synchronize_srcu", and the other RCU primitives. Or grab one
|
| /Linux-v5.10/tools/memory-model/Documentation/ |
| 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
195 Reading code using these primitives is often also quite helpful.
223 Unordered primitives such as atomic_read(), atomic_set(), READ_ONCE(), and
224 WRITE_ONCE() can safely be used in some cases. These primitives provide
[all …]
|
| /Linux-v5.10/drivers/staging/clocking-wizard/ |
| D | TODO | 5 refactoring of the clk primitives: https://lkml.org/lkml/2014/9/5/766)
|
| /Linux-v5.10/Documentation/devicetree/bindings/mailbox/ |
| D | nvidia,tegra186-hsp.txt | 4 together. It provides a set of hardware synchronization primitives for
6 protocols can use hardware synchronization primitives, when operating between
|
| /Linux-v5.10/tools/testing/selftests/powerpc/ |
| D | Makefile | 25 primitives \
|
| /Linux-v5.10/include/linux/ |
| D | intel_rapl.h | 67 u64 primitives[NR_RAPL_PRIMITIVES]; member
|
| /Linux-v5.10/Documentation/core-api/ |
| 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
|
| D | index.rst | 47 Concurrency primitives
|
| D | refcount-vs-atomic.rst | 39 compare-and-swap primitives.
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| 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
135 calls (where the underlying DMA primitives have changed), most of them can
|
| /Linux-v5.10/Documentation/locking/ |
| 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-v5.10/Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra210-bpmp.txt | 16 - reg: physical base address and length for HW synchornization primitives
|
| /Linux-v5.10/Documentation/process/ |
| 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-v5.10/Documentation/driver-api/ |
| D | i2c.rst | 35 operations, either using I2C primitives or by issuing SMBus commands to
|
| /Linux-v5.10/Documentation/staging/ |
| D | speculation.rst | 73 primitives.
|
| /Linux-v5.10/tools/testing/selftests/futex/ |
| D | README | 11 primitives. These can be used as is in user applications or can serve as
|
| /Linux-v5.10/Documentation/ |
| 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
|
| /Linux-v5.10/kernel/ |
| D | Kconfig.preempt | 64 various locking primitives (spinlocks, rwlocks, etc.) with
|
| /Linux-v5.10/drivers/crypto/caam/ |
| D | Kconfig | 142 Supported cryptographic primitives: encryption, decryption,
|
| /Linux-v5.10/Documentation/arm64/ |
| D | pointer-authentication.rst | 16 The ARMv8.3 Pointer Authentication extension adds primitives that can be
|
123
