Lines Matching full:critical

104 	critical sections.
166 	reclaimer that the reader is entering an RCU read-side critical
168 	critical section, though kernels built with CONFIG_PREEMPT_RCU
169 	can preempt RCU read-side critical sections.  Any RCU-protected
170 	data structure accessed during an RCU read-side critical section
172 	critical section.  Reference counts may be used in conjunction
176 	or interrupts also enters an RCU read-side critical section.
177 	Acquiring a spinlock also enters an RCU read-side critical
180 	Sleeplocks do *not* enter RCU read-side critical sections.
187 	reclaimer that the reader is exiting an RCU read-side critical
189 	or interrupts also exits an RCU read-side critical section.
190 	Releasing a spinlock also exits an RCU read-side critical section.
192 	Note that RCU read-side critical sections may be nested and/or
201 	all pre-existing RCU read-side critical sections on all CPUs
203 	necessarily wait for any subsequent RCU read-side critical
217 	read-side critical sections to complete, not necessarily for
221 	**immediately** after the last pre-existing RCU read-side critical
236 	critical sections have completed.  This callback variant is
312 	if an update happened while in the critical section, and incur
316 	only within the enclosing RCU read-side critical section [1]_.
327 	Holding a reference from one RCU read-side critical section
329 	one lock-based critical section to another!  Similarly,
330 	using a reference outside of the critical section in which
343 	of an RCU read-side critical section as long as the usage is
360 	invoked outside of an RCU read-side critical section and without
500 	read-side critical sections.
502 -	Within an RCU read-side critical section, use rcu_dereference()
517 	RCU read-side critical sections that might be referencing that
607 	read-side critical sections that might be referencing that
654 one read-side critical section to another.  It also assumes recursive
701 that once synchronize_rcu() exits, all RCU read-side critical sections
762 Remember that it is illegal to block while in an RCU read-side critical
764 that it must have completed all preceding RCU read-side critical sections.
766 RCU read-side critical sections will have completed.
770 that there are no RCU read-side critical sections holding a reference
785 		critical section, what the heck do you do in
907 critical sections can now run concurrently.  In many cases, this will
1056 	Critical sections	Grace period		Barrier
1067 	Critical sections	Grace period		Barrier
1080 	Critical sections	Grace period		Barrier
1096 	Critical sections	Grace period		Barrier
1104 	Critical sections	Grace period		Barrier
1112 	Critical sections	Grace period		Barrier
1120 	Critical sections	Grace period		Barrier
1187 g.	Do you need read-side critical sections that are respected even
1237 		consider task A in an RCU read-side critical section
1246 		approach where tasks in RCU read-side critical sections
1282 		critical section, what the heck do you do in
1287 		critical sections, it permits preemption of RCU
1288 		read-side critical sections.  It also permits
1289 		spinlocks blocking while in RCU read-side critical