Documentation/RCU/whatisRCU.rst

95 	critical sections.
157 	entering an RCU read-side critical section.  It is illegal
158 	to block while in an RCU read-side critical section, though
160 	read-side critical sections.  Any RCU-protected data structure
161 	accessed during an RCU read-side critical section is guaranteed to
162 	remain unreclaimed for the full duration of that critical section.
171 	exiting an RCU read-side critical section.  Note that RCU
172 	read-side critical sections may be nested and/or overlapping.
180 	read-side critical sections on all CPUs have completed.
182 	any subsequent RCU read-side critical sections to complete.
195 	read-side critical sections to complete, not necessarily for
199 	**immediately** after the last pre-existing RCU read-side critical
213 	after all ongoing RCU read-side critical sections have completed.
279 	if an update happened while in the critical section, and incur
283 	only within the enclosing RCU read-side critical section [1]_.
294 	Holding a reference from one RCU read-side critical section
296 	one lock-based critical section to another!  Similarly,
297 	using a reference outside of the critical section in which
310 	of an RCU read-side critical section as long as the usage is
327 	invoked outside of an RCU read-side critical section and without
463 	read-side critical sections.
465 -	Within an RCU read-side critical section, use rcu_dereference()
480 	RCU read-side critical sections that might be referencing that
572 	read-side critical sections that might be referencing that
611 one read-side critical section to another.  It also assumes recursive
658 that once synchronize_rcu() exits, all RCU read-side critical sections
719 Remember that it is illegal to block while in an RCU read-side critical
721 that it must have completed all preceding RCU read-side critical sections.
723 RCU read-side critical sections will have completed.
727 that there are no RCU read-side critical sections holding a reference
742 		critical section, what the heck do you do in
864 critical sections can now run concurrently.  In many cases, this will
1029 f.	Do you need read-side critical sections that are respected
1078 		consider task A in an RCU read-side critical section
1087 		approach where tasks in RCU read-side critical sections
1123 		critical section, what the heck do you do in
1128 		critical sections, it permits preemption of RCU
1129 		read-side critical sections.  It also permits
1130 		spinlocks blocking while in RCU read-side critical