Lines Matching refs:readers
28 RCU does allow -readers- to run (almost) naked, but -writers- must
60 The whole point of RCU is to permit readers to run without
61 any locks or atomic operations. This means that readers will
74 locks (that are acquired by both readers and writers)
76 the readers refrain from accessing can be guarded by
81 c. Make updates appear atomic to readers. For example,
85 appear to be atomic to RCU readers, nor will sequences
91 readers see valid data at all phases of the update.
134 is common to readers and updaters. However, lockdep
153 readers. Similarly, if the hlist macros are being used,
202 corresponding readers must use rcu_read_lock() and
204 synchronize_rcu_bh(), then the corresponding readers must
207 the corresponding readers must disable preemption, possibly
210 the corresponding readers must use srcu_read_lock() and
304 shared between readers and updaters. Additional primitives
399 is to wait until all pre-existing readers have finished before
402 that readers can follow that could be affected by the
406 Because these primitives only wait for pre-existing readers, it
408 readers will execute safely.