Lines Matching full: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
86 	The whole point of RCU is to permit readers to run without
87 	any locks or atomic operations.  This means that readers will
100 		locks (that are acquired by both readers and writers)
101 		that guard per-element state.  Fields that the readers
107 	c.	Make updates appear atomic to readers.	For example,
111 		appear to be atomic to RCU readers, nor will sequences
119 	d.	Carefully order the updates and the reads so that readers
139 	a.	Readers must maintain proper ordering of their memory
162 		is common to readers and updaters.  However, lockdep
181 		readers.  Similarly, if the hlist macros are being used,
233 	the corresponding readers may use:  (1) rcu_read_lock() and
239 	or call_srcu(), then the corresponding readers must use
247 		call_rcu_tasks(), then the readers must refrain from
253 		corresponding readers must use rcu_read_lock_trace()
257 		then the corresponding readers must use anything that
270 	that this usage is safe is that readers can use anything that
352 	shared between readers and updaters.  Additional primitives
357 	time that readers might be accessing that structure.  In such
439 	when you need lightweight readers.
456 	is to wait until all pre-existing readers have finished before
459 	that readers can follow that could be affected by the
463 	Because these primitives only wait for pre-existing readers, it
465 	readers will execute safely.
473 	For SRCU readers, you can use smp_mb__after_srcu_read_unlock()