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
85 	The whole point of RCU is to permit readers to run without
86 	any locks or atomic operations.  This means that readers will
99 		locks (that are acquired by both readers and writers)
101 		the readers refrain from accessing can be guarded by
106 	c.	Make updates appear atomic to readers.	For example,
110 		appear to be atomic to RCU readers, nor will sequences
116 		readers see valid data at all phases of the update.
156 		is common to readers and updaters.  However, lockdep
175 		readers.  Similarly, if the hlist macros are being used,
224 	the corresponding readers may use:  (1) rcu_read_lock() and
230 	or call_srcu(), then the corresponding readers must use
236 	then the readers must refrain from executing voluntary
239 	the corresponding readers must use rcu_read_lock_trace() and
241 	or synchronize_rcu_tasks_rude(), then the corresponding readers
253 	that this usage is safe is that readers can use anything that
333 	shared between readers and updaters.  Additional primitives
338 	time that readers might be accessing that structure.  In such
409 	when you need lightweight readers.
420 	is to wait until all pre-existing readers have finished before
423 	that readers can follow that could be affected by the
427 	Because these primitives only wait for pre-existing readers, it
429 	readers will execute safely.
437 	For SRCU readers, you can use smp_mb__after_srcu_read_unlock()