Lines Matching refs:critical

83 	critical sections.
143 	entering an RCU read-side critical section.  It is illegal
144 	to block while in an RCU read-side critical section, though
146 	read-side critical sections.  Any RCU-protected data structure
147 	accessed during an RCU read-side critical section is guaranteed to
148 	remain unreclaimed for the full duration of that critical section.
157 	exiting an RCU read-side critical section.  Note that RCU
158 	read-side critical sections may be nested and/or overlapping.
166 	read-side critical sections on all CPUs have completed.
168 	any subsequent RCU read-side critical sections to complete.
181 	read-side critical sections to complete, not necessarily for
185 	-immediately- after the last pre-existing RCU read-side critical
199 	after all ongoing RCU read-side critical sections have completed.
265 	if an update happened while in the critical section, and incur
269 	only within the enclosing RCU read-side critical section.
280 	Holding a reference from one RCU read-side critical section
282 	one lock-based critical section to another!  Similarly,
283 	using a reference outside of the critical section in which
424 	read-side critical sections.
426 o	Within an RCU read-side critical section, use rcu_dereference()
441 	RCU read-side critical sections that might be referencing that
530 	read-side critical sections that might be referencing that
567 one read-side critical section to another.  It also assumes recursive
614 that once synchronize_rcu() exits, all RCU read-side critical sections
670 Remember that it is illegal to block while in an RCU read-side critical
672 that it must have completed all preceding RCU read-side critical sections.
674 RCU read-side critical sections will have completed.
678 that there are no RCU read-side critical sections holding a reference
685 		critical section, what the heck do you do in
798 critical sections can now run concurrently.  In many cases, this will
944 f.	Do you need read-side critical sections that are respected
989 		consider task A in an RCU read-side critical section
998 		approach where tasks in RCU read-side critical sections
1027 		critical section, what the heck do you do in
1031 		critical sections, it permits preemption of RCU
1032 		read-side critical sections.  It also permits
1033 		spinlocks blocking while in RCU read-side critical