Lines Matching refs:side
94 b. Wait for all previous readers to complete their RCU read-side
157 entering an RCU read-side critical section. It is illegal
158 to block while in an RCU read-side critical section, though
160 read-side critical sections. Any RCU-protected data structure
161 accessed during an RCU read-side critical section is guaranteed to
171 exiting an RCU read-side critical section. Note that RCU
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
199 **immediately** after the last pre-existing RCU read-side critical
213 after all ongoing RCU read-side critical sections have completed.
215 it is illegal to block or where update-side performance is
283 only within the enclosing RCU read-side critical section [1]_.
294 Holding a reference from one RCU read-side critical section
310 of an RCU read-side critical section as long as the usage is
311 protected by locks acquired by the update-side code. This variant
323 update-side code as well as by RCU readers, then an additional
327 invoked outside of an RCU read-side critical section and without
362 above shows the most common one. On the updater side, the rcu_assign_pointer(),
364 flavors. However for protection (on the reader side), the primitives used vary
463 read-side critical sections.
465 - Within an RCU read-side critical section, use rcu_dereference()
480 RCU read-side critical sections that might be referencing that
571 read-side critical sections that might be referencing that
610 one read-side critical section to another. It also assumes recursive
657 that once synchronize_rcu() exits, all RCU read-side critical sections
705 read-side overhead is precisely zero, at least on non-Alpha CPUs.
718 Remember that it is illegal to block while in an RCU read-side critical
720 that it must have completed all preceding RCU read-side critical sections.
722 RCU read-side critical sections will have completed.
726 that there are no RCU read-side critical sections holding a reference
732 Give an example where Classic RCU's read-side
740 If it is illegal to block in an RCU read-side
806 Or, for those who prefer a side-by-side listing::
857 Either way, the differences are quite small. Read-side locking moves
858 to rcu_read_lock() and rcu_read_unlock, update-side locking moves from
862 However, there is one potential catch: the read-side and update-side
1028 f. Do you need read-side critical sections that are respected
1077 consider task A in an RCU read-side critical section
1081 read_acquire rcu_gp_mutex. Task A's RCU read-side
1086 approach where tasks in RCU read-side critical sections
1092 Give an example where Classic RCU's read-side
1121 If it is illegal to block in an RCU read-side
1128 read-side critical sections. It also permits
1129 spinlocks blocking while in RCU read-side critical