Lines Matching refs:readers
30 One final exception is where RCU readers are used to prevent
40 RCU does allow *readers* to run (almost) naked, but *writers* must
80 The whole point of RCU is to permit readers to run without
81 any locks or atomic operations. This means that readers will
94 locks (that are acquired by both readers and writers)
96 the readers refrain from accessing can be guarded by
101 c. Make updates appear atomic to readers. For example,
105 appear to be atomic to RCU readers, nor will sequences
111 readers see valid data at all phases of the update.
152 is common to readers and updaters. However, lockdep
171 readers. Similarly, if the hlist macros are being used,
217 the corresponding readers may use: (1) rcu_read_lock() and
223 or call_srcu(), then the corresponding readers must use
229 then the readers must refrain from executing voluntary
232 the corresponding readers must use rcu_read_lock_trace() and
234 or synchronize_rcu_tasks_rude(), then the corresponding readers
246 that this usage is safe is that readers can use anything that
325 shared between readers and updaters. Additional primitives
330 time that readers might be accessing that structure. In such
401 when you need lightweight readers.
412 is to wait until all pre-existing readers have finished before
415 that readers can follow that could be affected by the
419 Because these primitives only wait for pre-existing readers, it
421 readers will execute safely.
429 For SRCU readers, you can use smp_mb__after_srcu_read_unlock()