Searched refs:expedited (Results 1 – 6 of 6) sorted by relevance
| /linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| H A D | Expedited-Grace-Periods.rst | 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
[all …]
|
| /linux/include/uapi/linux/ |
| H A D | x25.h | 123 __u8 expedited; member
|
| /linux/Documentation/RCU/ |
| H A D | checklist.rst | 217 The expedited forms of these primitives have the same semantics
218 as the non-expedited forms, but expediting is more CPU intensive.
219 Use of the expedited primitives should be restricted to rare
223 kernel boot parameter to completely disable expedited grace
226 In particular, if you find yourself invoking one of the expedited
229 a single non-expedited primitive to cover the entire batch.
231 expedited primitive, and will be much much easier on the rest
247 srcu_struct. The rules for the expedited RCU grace-period-wait
248 primitives are the same as for their non-expedited counterparts.
451 SRCU's expedited primitive (synchronize_srcu_expedited())
|
| /linux/kernel/rcu/ |
| H A D | Kconfig | 255 blocking an expedited RCU grace period is boosted immediately.
260 bool "Perform RCU expedited work in a real-time kthread"
264 Use this option to further reduce the latencies of expedited
268 disable expedited grace periods after boot by unconditionally
|
| /linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 157 events, maintains ``rcu_barrier()`` state, tracks expedited
470 current expedited grace period. An expedited grace period has the same
471 conceptual properties as a normal grace period, but the expedited
479 expedited grace periods, respectively.
543 periods and in ``->exp_tasks`` for expedited grace periods. These last
553 RCU read-side critical section, then an expedited grace period started,
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 1796 | all synchronous grace periods are handled by the expedited |
1797 | grace-period mechanism. At runtime, this expedited mechanism relies |
1799 | drives the desired expedited grace period. Because dead-zone |
1801 | dead zone ends, expedited grace periods go back to using workqueues, |
1803 | user task received a POSIX signal while driving an expedited grace |
2663 SRCU also differs from other RCU flavors in that SRCU's expedited and
2664 non-expedited grace periods are implemented by the same mechanism. This
2672 period, that invocation will be automatically expedited.
2820 well as zero interprocessor interrupts undertaken during an expedited
|