Lines Matching refs:primitives
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
196 The expedited forms of these primitives have the same semantics
199 to real-time workloads. Use of the expedited primitives should
207 primitives repeatedly in a loop, please do everyone a favor:
226 the expedited primitives are the same as for their non-expedited
298 Note that although these primitives do take action to avoid memory
305 9. All RCU list-traversal primitives, which include
310 rcu_read_lock() and rcu_read_unlock(), or by similar primitives
316 primitives when the update-side lock is held is that doing so
318 shared between readers and updaters. Additional primitives
346 expedited forms of the three primitives, namely call_rcu(),
425 Because these primitives only wait for pre-existing readers, it
429 16. The various RCU read-side primitives do -not- necessarily contain
433 RCU update-side primitives to deal with this.