Searched refs:primitives (Results 1 – 25 of 48) sorted by relevance
12
| /Linux-v4.19/Documentation/RCU/ |
| D | checklist.txt | 24 read-side primitives is critically important.
56 rcu_read_lock() and friends? These primitives are needed
82 primitives to add, remove, and replace elements on
99 appear atomic, as will individual atomic primitives.
102 of multiple atomic primitives.
145 various "_rcu()" list-traversal primitives, such
149 primitives. This is particularly useful in code that
156 list-traversal primitives can substitute for a good
160 and list_add_rcu() primitives must be used in order
172 The list_replace_rcu() and hlist_replace_rcu() primitives
[all …]
|
| D | lockdep.txt | 10 In addition, RCU provides the following primitives that check lockdep's
24 checking of rcu_dereference() primitives:
100 and RCU list-/tree-traversal primitives, which do not (yet) check for
102 versions of these primitives might be created.
|
| D | 00-INDEX | 20 - RCU list primitives for use with SLAB_TYPESAFE_BY_RCU
|
| D | rcu_dereference.txt | 4 the similar primitives without worries. Dereferencing (prefix "*"),
11 o You must use one of the rcu_dereference() family of primitives
15 Without one of the rcu_dereference() primitives, compilers
148 kernel's wide array of primitives that cause code to
|
| D | listRCU.txt | 72 become list_for_each_entry_rcu(). The _rcu() list-traversal primitives
147 The list_del(), list_add(), and list_add_tail() primitives have been
149 The _rcu() list-manipulation primitives add memory barriers that are
|
| D | whatisRCU.txt | 231 the _rcu list-manipulation primitives such as list_add_rcu().
293 primitives, such as list_for_each_entry_rcu().
327 The rcu_dereference() and rcu_assign_pointer() primitives are used for
328 all three mechanisms, but different defer and protect primitives are
436 rcu_assign_pointer() primitives from interfering with each other.
548 in terms of familiar locking primitives, and another that more closely
564 familiar locking primitives. Its overhead makes it a non-starter for
|
| D | rcu.txt | 58 primitives. Or grab one of the cscope databases from:
|
| D | torture.txt | 31 primitives.
34 primitives. If both gp_normal and gp_exp are set, or
|
| /Linux-v4.19/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-v4.19/drivers/staging/clocking-wizard/ |
| D | TODO | 5 refactoring of the clk primitives: https://lkml.org/lkml/2014/9/5/766)
|
| /Linux-v4.19/Documentation/isdn/ |
| D | README.concap | 80 some basic connection control primitives are supported. The type and
92 service primitives to the network device.
104 The network interface driver accesses those primitives via callbacks
135 Protocols that don't process these primitives might fill in
146 some service primitives to the encapsulation protocol:
152 The encapsulation protocol accesses those primitives via callbacks
|
| /Linux-v4.19/tools/testing/selftests/powerpc/ |
| D | Makefile | 24 primitives \
|
| /Linux-v4.19/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-v4.19/Documentation/core-api/ |
| D | genericirq.rst | 121 primitives referenced by the assigned chip descriptor structure.
181 The helper functions call the chip primitives and are used by the
277 The simple flow handler does not call any handler/chip primitives.
365 These primitives are strictly intended to mean what they say: ack means
384 chip primitives. The per-irq structure is protected via desc->lock, by
|
| D | refcount-vs-atomic.rst | 39 compare-and-swap primitives.
|
| /Linux-v4.19/Documentation/ |
| D | atomic_t.txt | 164 Fully ordered primitives are ordered against everything prior and everything
177 ordering on their SMP atomic primitives. For example our TSO architectures
|
| D | speculation.txt | 71 primitives.
|
| /Linux-v4.19/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-v4.19/tools/memory-model/ |
| D | README | 154 relations on the locking primitives.
188 operations, locking primitives, and RCU is not provided.
|
| /Linux-v4.19/Documentation/driver-api/ |
| D | i2c.rst | 35 operations, either using I2C primitives or by issuing SMBus commands to
|
| /Linux-v4.19/tools/testing/selftests/futex/ |
| D | README | 11 primitives. These can be used as is in user applications or can serve as
|
| /Linux-v4.19/drivers/crypto/caam/ |
| D | Kconfig | 127 Supported cryptographic primitives: encryption, decryption,
|
| /Linux-v4.19/drivers/powercap/ |
| D | intel_rapl.c | 138 u64 primitives[NR_RAPL_PRIMITIVES]; member
821 *data = rd->rdd.primitives[prim]; in rapl_read_data_raw()
1194 rp->domains[dmn].rdd.primitives[prim] = val; in rapl_update_domain_data()
|
| /Linux-v4.19/Documentation/locking/ |
| D | locktorture.txt | 6 that runs torture tests on core kernel locking primitives. The kernel
|
| D | lockdep-design.txt | 149 versions of the various locking primitives were added that allow you to
168 Note: When changing code to use the _nested() primitives, be careful and
|
12
