Lines Matching full:side
98 b. Wait for all previous readers to complete their RCU read-side
161 entering an RCU read-side critical section. It is illegal
162 to block while in an RCU read-side critical section, though
164 read-side critical sections. Any RCU-protected data structure
165 accessed during an RCU read-side critical section is guaranteed to
175 exiting an RCU read-side critical section. Note that RCU
176 read-side critical sections may be nested and/or overlapping.
184 read-side critical sections on all CPUs have completed.
186 any subsequent RCU read-side critical sections to complete.
199 read-side critical sections to complete, not necessarily for
203 **immediately** after the last pre-existing RCU read-side critical
217 after all ongoing RCU read-side critical sections have completed.
219 it is illegal to block or where update-side performance is
287 only within the enclosing RCU read-side critical section [1]_.
298 Holding a reference from one RCU read-side critical section
314 of an RCU read-side critical section as long as the usage is
315 protected by locks acquired by the update-side code. This variant
327 update-side code as well as by RCU readers, then an additional
331 invoked outside of an RCU read-side critical section and without
366 above shows the most common one. On the updater side, the rcu_assign_pointer(),
368 flavors. However for protection (on the reader side), the primitives used vary
466 read-side critical sections.
468 - Within an RCU read-side critical section, use rcu_dereference()
483 RCU read-side critical sections that might be referencing that
573 read-side critical sections that might be referencing that
612 one read-side critical section to another. It also assumes recursive
659 that once synchronize_rcu() exits, all RCU read-side critical sections
707 read-side overhead is precisely zero, at least on non-Alpha CPUs.
720 Remember that it is illegal to block while in an RCU read-side critical
722 that it must have completed all preceding RCU read-side critical sections.
724 RCU read-side critical sections will have completed.
728 that there are no RCU read-side critical sections holding a reference
734 Give an example where Classic RCU's read-side
742 If it is illegal to block in an RCU read-side
808 Or, for those who prefer a side-by-side listing::
859 Either way, the differences are quite small. Read-side locking moves
860 to rcu_read_lock() and rcu_read_unlock, update-side locking moves from
864 However, there is one potential catch: the read-side and update-side
1113 f. Do you need read-side critical sections that are respected
1162 consider task A in an RCU read-side critical section
1166 read_acquire rcu_gp_mutex. Task A's RCU read-side
1171 approach where tasks in RCU read-side critical sections
1177 Give an example where Classic RCU's read-side
1206 If it is illegal to block in an RCU read-side
1213 read-side critical sections. It also permits
1214 spinlocks blocking while in RCU read-side critical