Lines Matching refs:idle

17 2.	Omit scheduling-clock ticks on idle CPUs (CONFIG_NO_HZ_IDLE=y or
21 3. Omit scheduling-clock ticks on CPUs that are either idle or that
37 that use short bursts of CPU, where there are very frequent idle
38 periods, but where these idle periods are also quite short (tens or
43 other than increasing the overhead of switching to and from idle and
49 However, if you are instead running a light workload with long idle
64 If a CPU is idle, there is little point in sending it a scheduling-clock
67 and an idle CPU has no duties to shift its attention among.
70 scheduling-clock interrupts to idle CPUs, which is critically important
78 idle CPUs. That said, dyntick-idle mode is not free:
81 to and from the idle loop.
83 2. On many architectures, dyntick-idle mode also increases the
88 in order to avoid degrading from-idle transition latencies.
90 An idle CPU that is not receiving scheduling-clock interrupts is said to
91 be "dyntick-idle", "in dyntick-idle mode", "in nohz mode", or "running
92 tickless". The remainder of this document will use "dyntick-idle mode".
95 dyntick-idle mode in CONFIG_NO_HZ_IDLE=y kernels by specifying "nohz=off".
97 dyntick-idle mode.
105 task implies also omitting them for idle CPUs.
115 wait idle while the delayed CPU finishes. Thus, the delay is multiplied
149 Just as with dyntick-idle mode, the benefits of adaptive-tick mode do
153 adaptive ticks without also running dyntick idle. This dependency
186 There are situations in which idle CPUs cannot be permitted to
187 enter either dyntick-idle mode or adaptive-tick mode, the most
191 to enter dyntick-idle mode or adaptive-tick mode anyway. In this case,
225 never prevents offloaded CPUs from entering either dyntick-idle mode
257 o Dyntick-idle slows transitions to and from idle slightly.
260 dyntick-idle mode, an option that most of them take. However,
268 b. On x86 systems, use the "idle=mwait" boot parameter.
273 d. On x86 systems, use the "idle=poll" boot parameter.
277 be even worse than that of dyntick-idle. Furthermore,
308 o A reboot is required to reconfigure both adaptive idle and RCU
332 o Unless all CPUs are idle, at least one CPU must keep the
338 going, even if all CPUs are otherwise idle.