Lines Matching refs:idle

44 idle injection across all online CPU threads was introduced. The goal
68 If the kernel can also inject idle time to the system, then a
71 control system, where the target set point is a user-selected idle
73 between the actual package level C-state residency ratio and the target idle
81 thread synchronizes its idle time and duration, based on the rounding
89 Alignment of idle time around jiffies ensures scalability for HZ
92 kidle_inject/cpu. During idle injection, it runs monitor/mwait idle
96 The NOHZ schedule tick is disabled during idle time, but interrupts
123 In terms of dynamics of the idle control system, package level idle
126 intel_powerclamp driver attempts to enforce the desired idle time
127 instantly as given input (target idle ratio). After injection,
128 powerclamp monitors the actual idle for a given time window and adjust
150 a) determine the effective range of idle injection ratio
157 	enter idle without extra wakeups (such as external interrupts).
160 	When an excessive amount of wakeups occurs during idle, an
161 	additional idle ratio can be added to quiet interrupts, by
209 To compensate for excessive amounts of wakeup during idle, additional
210 idle time is injected when such a condition is detected. Currently,
232 The maximum range that idle injection is allowed is capped at 50
234 forced idle time, excessive interrupts could result in less
237 case, little can be done from the idle injection threads. In most
244 with the changes. During this time, idle injection is out of sync,
247 ratio is updated much less frequently than the idle injection
253 Ivy Bridge system and the 80P Westmere server under 50% idle ratio.
255 target idle ratio. The compensation also increases as the idle ratio
274 cur_state allows user to set the desired idle percentage. Writing 0 to
275 cur_state will stop idle injection. Writing a value between 1 and
276 max_state will start the idle injection. Reading cur_state returns the
277 actual and current idle percentage. This may not be the same value
278 set by the user in that current idle percentage depends on workload
279 and includes natural idle. When idle injection is disabled, reading
284 - To inject 25% idle time::
288 If the system is not busy and has more than 25% idle time already,
289 then the powerclamp driver will not start idle injection. Using Top
290 will not show idle injection kernel threads.
293 idle time, powerclamp kernel threads will do idle injection. Forced
294 idle time is accounted as normal idle in that common code path is
295 taken as the idle task.
297 In this example, 24.1% idle is shown. This helps the system admin or