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.
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
197 The expedited forms of these primitives have the same semantics
200 to real-time workloads. Use of the expedited primitives should
208 primitives repeatedly in a loop, please do everyone a favor:
221 or any pair of primitives that disables and re-enables preemption,
226 the expedited primitives are the same as for their non-expedited
294 Note that although these primitives do take action to avoid memory
301 9. All RCU list-traversal primitives, which include
306 rcu_read_lock() and rcu_read_unlock(), or by similar primitives
312 primitives when the update-side lock is held is that doing so
314 shared between readers and updaters. Additional primitives
401 Because these primitives only wait for pre-existing readers, it
405 15. The various RCU read-side primitives do -not- necessarily contain
409 RCU update-side primitives to deal with this.