Lines Matching refs:sections

18 sections of code with "critical sections", and the update side will wait
19 for the execution of all *currently running* critical sections before
22 The key point here is that only the currently running critical sections
23 are waited for; critical sections that are started **after** the beginning
35 the old data.  Therefore, critical sections that begin after removal
36 do not matter; as soon as all previous critical sections have finished,
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