Lines Matching refs:primitives
24 read-side primitives is critically important.
46 rcu_read_lock() and friends? These primitives are needed
66 primitives to add, remove, and replace elements on
83 appear atomic, as will individual atomic primitives.
86 of multiple atomic primitives.
129 various "_rcu()" list-traversal primitives, such
133 primitives. This is particularly useful in code that
140 list-traversal primitives can substitute for a good
144 and list_add_rcu() primitives must be used in order
156 The list_replace_rcu() and hlist_replace_rcu() primitives
180 The expedited forms of these primitives have the same semantics
183 primitives should be restricted to rare configuration-change
188 primitives repeatedly in a loop, please do everyone a favor:
212 the expedited primitives are the same as for their non-expedited
284 Note that although these primitives do take action to avoid memory
291 9. All RCU list-traversal primitives, which include
296 rcu_read_lock() and rcu_read_unlock(), or by similar primitives
302 primitives when the update-side lock is held is that doing so
304 shared between readers and updaters. Additional primitives
332 expedited forms of the three primitives, namely call_rcu(),
406 Because these primitives only wait for pre-existing readers, it
410 16. The various RCU read-side primitives do -not- necessarily contain
414 RCU update-side primitives to deal with this.