Lines Matching refs:expedited
8 This document describes RCU's expedited grace periods.
10 high efficiency and minimal disturbance, expedited grace periods accept
20 The expedited RCU grace periods cannot be accused of being subtle,
22 has not yet provided a quiescent state for the current expedited
32 state, the expedited grace period has completed.
43 expedited grace period is shown in the following diagram:
54 Otherwise, the expedited grace period will use
72 block the current expedited grace period until it resumes and finds its
86 | Why not just have the expedited grace period check the state of all |
116 the handling of a given CPU by an RCU-sched expedited grace period is
140 The expedited nature of expedited grace periods require a much tighter
146 The interaction between expedited grace periods and CPU hotplug
152 have ever been online at the beginning of an RCU expedited grace
159 beginning of the most recent RCU expedited grace period. The
163 field has changed since the beginning of the last RCU expedited grace
168 RCU expedited grace period. This means that only those CPUs that have
224 Each expedited grace period checks for idle CPUs when initially forming
244 In summary, RCU expedited grace periods check for idle when building the
251 If each grace-period request was carried out separately, expedited grace
255 that a single expedited grace-period operation will cover all requests
260 has an odd value when there is an expedited grace period in progress and
269 #. ``rcu_exp_gp_seq_start()``, which marks the start of an expedited
271 #. ``rcu_exp_gp_seq_end()``, which marks the end of an expedited grace
274 #. ``rcu_exp_gp_seq_done()``, which returns ``true`` if a full expedited
289 the expedited grace period is to use the ``rcu_node`` combining tree, as
405 In earlier implementations, the task requesting the expedited grace
417 allows wakeups for the previous expedited grace period to be overlapped
418 with processing for the next expedited grace period. Because there are
422 expedited grace-period processing and the ``->exp_wake_mutex`` guard
435 readers take too long, and therefore expedited grace periods check for
443 | expedited grace periods? |
453 the expedited grace period to end, but with a timeout set to the current
462 The use of workqueues has the advantage that the expedited grace-period
468 zone”, expedited grace periods must do something else during this time.
471 requesting task drive the expedited grace period, as was the case before
477 Non-expedited non-SRCU synchronous grace periods must also operate
478 normally during mid-boot. This is handled by causing non-expedited grace
479 periods to take the expedited code path during mid-boot.
483 somehow arises, appropriate adjustments can be made to the expedited
505 tight synchronization between expedited grace periods and CPU-hotplug
513 expedited grace period are awakened. A pair of mutexes are used to allow
517 This combination of mechanisms allows expedited grace periods to run