Lines Matching full:sections

50 with example uses should focus on Sections 3 and 4.  People who need to
95 	critical sections.
160 	read-side critical sections.  Any RCU-protected data structure
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
213 	after all ongoing RCU read-side critical sections have completed.
463 	read-side critical sections.
480 	RCU read-side critical sections that might be referencing that
572 	read-side critical sections that might be referencing that
658 that once synchronize_rcu() exits, all RCU read-side critical sections
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
864 critical sections can now run concurrently.  In many cases, this will
934 	Critical sections	Grace period		Barrier
945 	Critical sections	Grace period		Barrier
958 	Critical sections	Grace period		Barrier
974 	Critical sections	Grace period		Barrier
1029 f.	Do you need read-side critical sections that are respected
1087 		approach where tasks in RCU read-side critical sections
1128 		critical sections, it permits preemption of RCU
1129 		read-side critical sections.  It also permits
1131 		sections.