Lines Matching full:side

103 b.	Wait for all previous readers to complete their RCU read-side
166 	reclaimer that the reader is entering an RCU read-side critical
167 	section.  It is illegal to block while in an RCU read-side
169 	can preempt RCU read-side critical sections.  Any RCU-protected
170 	data structure accessed during an RCU read-side critical section
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
235 	argument which are invoked after all ongoing RCU read-side
238 	or where update-side performance is critically important.
316 	only within the enclosing RCU read-side critical section [1]_.
327 	Holding a reference from one RCU read-side critical section
343 	of an RCU read-side critical section as long as the usage is
344 	protected by locks acquired by the update-side code.  This variant
356 	update-side code as well as by RCU readers, then an additional
360 	invoked outside of an RCU read-side critical section and without
398 above shows the most common one. On the updater side, the rcu_assign_pointer(),
400 flavors. However for protection (on the reader side), the primitives used vary
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
749 read-side overhead is precisely zero, at least on non-Alpha CPUs.
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
776 		Give an example where Classic RCU's read-side
784 		If it is illegal to block in an RCU read-side
850 Or, for those who prefer a side-by-side listing::
901 Either way, the differences are quite small.  Read-side locking moves
902 to rcu_read_lock() and rcu_read_unlock, update-side locking moves from
906 However, there is one potential catch: the read-side and update-side
1187 g.	Do you need read-side critical sections that are respected even
1237 		consider task A in an RCU read-side critical section
1241 		read_acquire rcu_gp_mutex.  Task A's RCU read-side
1246 		approach where tasks in RCU read-side critical sections
1252 		Give an example where Classic RCU's read-side
1281 		If it is illegal to block in an RCU read-side
1288 		read-side critical sections.  It also permits
1289 		spinlocks blocking while in RCU read-side critical