Lines Matching refs:primitives
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.
147 various "_rcu()" list-traversal primitives, such
151 primitives. This is particularly useful in code that
158 list-traversal primitives can substitute for a good
162 and list_add_rcu() primitives must be used in order
174 The list_replace_rcu() and hlist_replace_rcu() primitives
195 The expedited forms of these primitives have the same semantics
198 to real-time workloads. Use of the expedited primitives should
206 primitives repeatedly in a loop, please do everyone a favor:
218 rcu_read_unlock(), (2) any pair of primitives that disables
220 rcu_read_unlock_bh(), or (3) any pair of primitives that disables
226 primitives are the same as for their non-expedited counterparts.
239 when using non-obvious pairs of primitives, commenting is
305 Note that although these primitives do take action to avoid memory
312 9. All RCU list-traversal primitives, which include
317 rcu_read_lock() and rcu_read_unlock(), or by similar primitives
323 primitives when the update-side lock is held is that doing so
325 shared between readers and updaters. Additional primitives
419 Because these primitives only wait for pre-existing readers, it
423 15. The various RCU read-side primitives do *not* necessarily contain
427 RCU update-side primitives to deal with this.