Lines Matching refs:read

13 during the 2.5 development effort that is optimized for read-mostly
43 everything, feel free to read the whole thing -- but if you are really
77 b.	Wait for all previous readers to complete their RCU read-side
138 	entering an RCU read-side critical section.  It is illegal
139 	to block while in an RCU read-side critical section, though
141 	read-side critical sections.  Any RCU-protected data structure
142 	accessed during an RCU read-side critical section is guaranteed to
152 	exiting an RCU read-side critical section.  Note that RCU
153 	read-side critical sections may be nested and/or overlapping.
161 	read-side critical sections on all CPUs have completed.
163 	any subsequent RCU read-side critical sections to complete.
176 	read-side critical sections to complete, not necessarily for
180 	-immediately- after the last pre-existing RCU read-side critical
188 	to be useful in all but the most read-intensive situations,
194 	after all ongoing RCU read-side critical sections have completed.
262 	only within the enclosing RCU read-side critical section.
273 	Holding a reference from one RCU read-side critical section
417 	read-side critical sections.
419 o	Within an RCU read-side critical section, use rcu_dereference()
434 	RCU read-side critical sections that might be referencing that
523 	read-side critical sections that might be referencing that
560 one read-side critical section to another.
601 The rcu_read_lock() and rcu_read_unlock() primitive read-acquire
604 it.  This means that once synchronize_rcu() exits, all RCU read-side
644 read-side overhead is precisely zero, at least on non-Alpha CPUs.
657 Remember that it is illegal to block while in an RCU read-side critical
659 that it must have completed all preceding RCU read-side critical sections.
661 RCU read-side critical sections will have completed.
665 that there are no RCU read-side critical sections holding a reference
668 Quick Quiz #2:	Give an example where Classic RCU's read-side
671 Quick Quiz #3:  If it is illegal to block in an RCU read-side
776 However, there is one potential catch: the read-side and update-side
919 f.	Do you need read-side critical sections that are respected
964 		consider task A in an RCU read-side critical section
965 		(thus read-holding rcu_gp_mutex), task B blocked
968 		read_acquire rcu_gp_mutex.  Task A's RCU read-side
973 		approach where tasks in RCU read-side critical sections
976 Quick Quiz #2:	Give an example where Classic RCU's read-side
1001 Quick Quiz #3:  If it is illegal to block in an RCU read-side
1007 		read-side critical sections.  It also permits
1008 		spinlocks blocking while in RCU read-side critical