Lines Matching refs:side

106 b.	Wait for all previous readers to complete their RCU read-side
169 	reclaimer that the reader is entering an RCU read-side critical
170 	section.  It is illegal to block while in an RCU read-side
172 	can preempt RCU read-side critical sections.  Any RCU-protected
173 	data structure accessed during an RCU read-side critical section
179 	or interrupts also enters an RCU read-side critical section.
180 	Acquiring a spinlock also enters an RCU read-side critical
183 	Sleeplocks do *not* enter RCU read-side critical sections.
190 	reclaimer that the reader is exiting an RCU read-side critical
192 	or interrupts also exits an RCU read-side critical section.
193 	Releasing a spinlock also exits an RCU read-side critical section.
195 	Note that RCU read-side critical sections may be nested and/or
204 	all pre-existing RCU read-side critical sections on all CPUs
206 	necessarily wait for any subsequent RCU read-side critical
220 	read-side critical sections to complete, not necessarily for
224 	**immediately** after the last pre-existing RCU read-side critical
238 	argument which are invoked after all ongoing RCU read-side
241 	or where update-side performance is critically important.
319 	only within the enclosing RCU read-side critical section [1]_.
330 	Holding a reference from one RCU read-side critical section
346 	of an RCU read-side critical section as long as the usage is
347 	protected by locks acquired by the update-side code.  This variant
359 	update-side code as well as by RCU readers, then an additional
363 	invoked outside of an RCU read-side critical section and without
401 above shows the most common one. On the updater side, the rcu_assign_pointer(),
403 flavors. However for protection (on the reader side), the primitives used vary
503 	read-side critical sections.
505 -	Within an RCU read-side critical section, use rcu_dereference()
520 	RCU read-side critical sections that might be referencing that
610 	read-side critical sections that might be referencing that
657 one read-side critical section to another.  It also assumes recursive
704 that once synchronize_rcu() exits, all RCU read-side critical sections
752 read-side overhead is precisely zero, at least on non-Alpha CPUs.
765 Remember that it is illegal to block while in an RCU read-side critical
767 that it must have completed all preceding RCU read-side critical sections.
769 RCU read-side critical sections will have completed.
773 that there are no RCU read-side critical sections holding a reference
779 		Give an example where Classic RCU's read-side
787 		If it is illegal to block in an RCU read-side
853 Or, for those who prefer a side-by-side listing::
904 Either way, the differences are quite small.  Read-side locking moves
905 to rcu_read_lock() and rcu_read_unlock, update-side locking moves from
909 However, there is one potential catch: the read-side and update-side
1200 g.	Do you need read-side critical sections that are respected even
1250 		consider task A in an RCU read-side critical section
1254 		read_acquire rcu_gp_mutex.  Task A's RCU read-side
1259 		approach where tasks in RCU read-side critical sections
1265 		Give an example where Classic RCU's read-side
1294 		If it is illegal to block in an RCU read-side
1301 		read-side critical sections.  It also permits
1302 		spinlocks blocking while in RCU read-side critical