Lines Matching refs:side

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
194 	after all ongoing RCU read-side critical sections have completed.
196 	it is illegal to block or where update-side performance is
264 	only within the enclosing RCU read-side critical section.
275 	Holding a reference from one RCU read-side critical section
419 	read-side critical sections.
421 o	Within an RCU read-side critical section, use rcu_dereference()
436 	RCU read-side critical sections that might be referencing that
525 	read-side critical sections that might be referencing that
562 one read-side critical section to another.
606 it.  This means that once synchronize_rcu() exits, all RCU read-side
646 read-side overhead is precisely zero, at least on non-Alpha CPUs.
659 Remember that it is illegal to block while in an RCU read-side critical
661 that it must have completed all preceding RCU read-side critical sections.
663 RCU read-side critical sections will have completed.
667 that there are no RCU read-side critical sections holding a reference
670 Quick Quiz #2:	Give an example where Classic RCU's read-side
673 Quick Quiz #3:  If it is illegal to block in an RCU read-side
726 Or, for those who prefer a side-by-side listing:
773 Either way, the differences are quite small.  Read-side locking moves
774 to rcu_read_lock() and rcu_read_unlock, update-side locking moves from
778 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
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