Lines Matching refs:primitives
28 read-side primitives is critically important.
60 rcu_read_lock() and friends? These primitives are needed
92 primitives to add, remove, and replace elements on
109 appear atomic, as will individual atomic primitives.
112 of multiple atomic primitives. One alternative is to
157 various "_rcu()" list-traversal primitives, such
161 primitives. This is particularly useful in code that
168 list-traversal primitives can substitute for a good
172 and list_add_rcu() primitives must be used in order
184 The list_replace_rcu() and hlist_replace_rcu() primitives
211 The expedited forms of these primitives have the same semantics
213 Use of the expedited primitives should be restricted to rare
221 primitives repeatedly in a loop, please do everyone a favor:
228 primitives such as call_rcu().
234 rcu_read_unlock(), (2) any pair of primitives that disables
236 rcu_read_unlock_bh(), or (3) any pair of primitives that disables
242 primitives are the same as for their non-expedited counterparts.
263 when using non-obvious pairs of primitives, commenting is
332 Note that although these primitives do take action to avoid
339 9. All RCU list-traversal primitives, which include
344 rcu_read_lock() and rcu_read_unlock(), or by similar primitives
350 primitives when the update-side lock is held is that doing so
352 shared between readers and updaters. Additional primitives
463 Because these primitives only wait for pre-existing readers, it
467 15. The various RCU read-side primitives do *not* necessarily contain
471 RCU update-side primitives to deal with this.