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 moniors 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
272 - To inject 25% idle time
276 If the system is not busy and has more than 25% idle time already,
277 then the powerclamp driver will not start idle injection. Using Top
278 will not show idle injection kernel threads.
281 idle time, powerclamp kernel threads will do idle injection, which
282 appear running to the scheduler. But the overall system idle is still
283 reflected. In this example, 24.1% idle is shown. This helps the