Lines Matching refs:idle
42 idle injection across all online CPU threads was introduced. The goal
66 If the kernel can also inject idle time to the system, then a
69 control system, where the target set point is a user-selected idle
71 between the actual package level C-state residency ratio and the target idle
79 thread synchronizes its idle time and duration, based on the rounding
87 Alignment of idle time around jiffies ensures scalability for HZ
90 kidle_inject/cpu. During idle injection, it runs monitor/mwait idle
94 The NOHZ schedule tick is disabled during idle time, but interrupts
119 In terms of dynamics of the idle control system, package level idle
122 intel_powerclamp driver attempts to enforce the desired idle time
123 instantly as given input (target idle ratio). After injection,
124 powerclamp monitors the actual idle for a given time window and adjust
146 a) determine the effective range of idle injection ratio
153 enter idle without extra wakeups (such as external interrupts).
156 When an excessive amount of wakeups occurs during idle, an
157 additional idle ratio can be added to quiet interrupts, by
204 To compensate for excessive amounts of wakeup during idle, additional
205 idle time is injected when such a condition is detected. Currently,
228 The maximum range that idle injection is allowed is capped at 50
230 forced idle time, excessive interrupts could result in less
233 case, little can be done from the idle injection threads. In most
240 with the changes. During this time, idle injection is out of sync,
243 ratio is updated much less frequently than the idle injection
249 Ivy Bridge system and the 80P Westmere server under 50% idle ratio.
251 target idle ratio. The compensation also increases as the idle ratio
271 cur_state allows user to set the desired idle percentage. Writing 0 to
272 cur_state will stop idle injection. Writing a value between 1 and
273 max_state will start the idle injection. Reading cur_state returns the
274 actual and current idle percentage. This may not be the same value
275 set by the user in that current idle percentage depends on workload
276 and includes natural idle. When idle injection is disabled, reading
281 - To inject 25% idle time
285 If the system is not busy and has more than 25% idle time already,
286 then the powerclamp driver will not start idle injection. Using Top
287 will not show idle injection kernel threads.
290 idle time, powerclamp kernel threads will do idle injection. Forced
291 idle time is accounted as normal idle in that common code path is
292 taken as the idle task.
294 In this example, 24.1% idle is shown. This helps the system admin or