Lines Matching full:side

6 on the read side (it is wait-free), and thus can make the read paths
10 thus it is not used alone.  Typically, the write-side will use a lock to
17 RCU is fundamentally a "wait-to-finish" mechanism.  The read side marks
18 sections of code with "critical sections", and the update side will wait
67         entering an RCU read-side critical section.
71         exiting an RCU read-side critical section.  Note that RCU
72         read-side critical sections may be nested and/or overlapping.
75         Blocks until all pre-existing RCU read-side critical sections
87         read-side critical sections on all threads have completed.  This
135         case when using RCU, because read-side critical sections typically
140         RCU read-side critical sections must use ``qatomic_rcu_read()`` to
144         Furthermore, RCU read-side critical sections should traverse the
160         order as reads in the RCU read-side critical sections (or if
200   programming; not allowing this would prevent upgrading an RCU read-side
243 read-side critical section in progress, the RCU read-side primitives
252 The RCU read-side critical section ensures that the value of ``p`` remains
255 The write side looks simply like this (with appropriate locking)::
274 The write side can be like this::
291 In both cases, the write side only performs removal.  Reclamation
294 last reference may be dropped on the read side.  Hence you can
326 out of the write-side critical section.
339 - avoiding mismatches in the read side between the array data and the
364     read side:
371     write side (running under a lock):