Lines Matching refs:period
13 grace-period memory ordering guarantee is provided.
20 Any code that happens after the end of a given RCU grace period is guaranteed
22 period that are within RCU read-side critical sections.
24 period is guaranteed to not see the effects of all accesses following the end
25 of that grace period that are within RCU read-side critical sections.
34 two phases, one of which is executed before the grace period and
35 the other of which is executed after the grace period.
49 The workhorse for RCU's grace-period memory ordering is the
74 period, including any CPUs that came online or went offline during
75 the grace period in question.
119 | that new readers will see all of the updater's pre-grace-period |
120 | accesses and also guarantees that the updater's post-grace-period |
126 | Because we must provide ordering for RCU's polling grace-period |
145 RCU's grace-period memory ordering guarantee to extend to any
152 The grace-period kthread invokes ``rcu_dynticks_snap()`` and
159 | But what about CPUs that remain offline for the entire grace period? |
163 | Such CPUs will be offline at the beginning of the grace period, so |
164 | the grace period won't expect quiescent states from them. Races |
165 | between grace-period start and CPU-hotplug operations are mediated |
172 a CPU that is not yet aware that the grace period has ended, and thus
173 might not yet be subject to the grace period's memory ordering.
193 Tree RCU's grace--period memory-ordering guarantees rely most heavily on
254 Tree RCU's grace-period memory-ordering guarantee is provided by a
272 If RCU's grace-period guarantee is to mean anything at all, any access
274 happen before the corresponding grace period. The implementation of this
275 portion of RCU's grace period guarantee is shown in the following
285 period until a later call to ``rcu_accelerate_cbs()``, as shown in the
301 There are a few other code paths within grace-period processing that
304 with a future grace-period number under the protection of the CPU's lead
313 update) happen before the start of the corresponding grace period.
330 Grace-period initialization is carried out by the grace-period kernel
333 ordering through the grace-period computation will require duplicating
336 to keep the ``rcu_node`` river tractable, the grace-period kernel
338 section with the various phases of grace-period initialization.
340 The first ordering-related grace-period initialization action is to
341 advance the ``rcu_state`` structure's ``->gp_seq`` grace-period-number
352 grace period. In the common case where the number of online CPUs for
376 ``__note_gp_changes()`` to notice that a new grace period has started,
377 as described in the next section. But because the grace-period kthread
378 started the grace period at the root (with the advancing of the
381 the start of the grace period will happen after the actual start of the
382 grace period.
387 | But what about the CPU that started the grace period? Why wouldn't it |
388 | see the start of the grace period right when it started that grace |
389 | period? |
394 | CPU starting the grace period is immediately aware of having done so. |
396 | the CPU starting the grace period does not really become aware of the |
397 | start of this grace period until its first call to |
407 When all entities that might block the grace period have reported
409 states reported on their behalf), the grace period can end. Online
416 end of the grace period. Earlier quiescent states would push up the
424 point that CPU will notice the start of a new grace period while holding
426 diagram happens after the start of the grace period. In addition, this
429 grace period, and thus a critical section that the grace period must
436 | beginning of the grace period (the advancing of ``->gp_seq`` from |
437 | earlier), so why should the grace period wait on such a critical |
442 | It is indeed not necessary for the grace period to wait on such a |
445 | more scalable than a “big bang” all-at-once grace-period start could |
461 apply to the current grace period, it invokes ``rcu_report_rnp()`` which
490 The RCU grace-period kernel thread samples the per-CPU idleness variable
493 precede the idle period (the oval near the top of the diagram above)
494 will happen before the end of the current grace period. Similarly, the
495 beginning of the current grace period will happen before any RCU
496 read-side critical sections that follow the idle period (the oval near
499 Plumbing this into the full grace-period execution is described
516 ``->qsmaskinitnext``. The RCU grace-period kernel thread samples this
518 grace period.
520 Plumbing this into the full grace-period execution is described
527 states, and therefore the grace-period kernel thread must do the
549 | subordinate to that structure on which the current grace period is |
551 | root ended the grace period? |
565 Grace-period cleanup first scans the ``rcu_node`` tree breadth-first
572 As indicated by the oval at the bottom of the diagram, once grace-period
573 cleanup is complete, the next grace period can begin.
578 | But when precisely does the grace period end? |
582 | There is no useful single point at which the grace period can be said |
597 waiting for this grace period to end. These callbacks are identified by
615 period.
622 important, consider the top half of the `grace-period
626 the rightmost leaf ``rcu_node`` structure, and the grace-period kernel
628 grace period's memory ordering might not yet have reached that CPU, so