Lines Matching full:sections

59 with example uses should focus on Sections 3 and 4.  People who need to
104 	critical sections.
169 	can preempt RCU read-side critical sections.  Any RCU-protected
178 	sections, even for spinlocks that do not disable preemption,
180 	Sleeplocks do *not* enter RCU read-side critical sections.
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
204 	sections to complete.  For example, consider the following
217 	read-side critical sections to complete, not necessarily for
236 	critical sections have completed.  This callback variant is
500 	read-side critical sections.
517 	RCU read-side critical sections that might be referencing that
607 	read-side critical sections that might be referencing that
701 that once synchronize_rcu() exits, all RCU read-side critical sections
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
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
1246 		approach where tasks in RCU read-side critical sections
1287 		critical sections, it permits preemption of RCU
1288 		read-side critical sections.  It also permits
1290 		sections.