Lines Matching full:scheduler

157 all of the online CPUs belonging to the given policy with the CPU scheduler.
158 The utilization update callbacks will be invoked by the CPU scheduler on
160 scheduler tick or generally whenever the CPU utilization may change (from the
161 scheduler's perspective).  They are expected to carry out computations needed
165 scheduler context or asynchronously, via a kernel thread or workqueue, depending
186 callbacks are invoked by the CPU scheduler in the same way as for scaling
188 use and change the hardware configuration accordingly in one go from scheduler
387 This governor uses CPU utilization data available from the CPU scheduler.  It
388 generally is regarded as a part of the CPU scheduler, so it can access the
389 scheduler's internal data structures directly.
391 It runs entirely in scheduler context, although in some cases it may need to
394 is capable of changing the CPU frequency from scheduler context).
416 is passed by the scheduler to the governor callback which causes the frequency
427 	The purpose of this tunable is to reduce the scheduler context overhead
432 tightly integrated with the CPU scheduler, its overhead in terms of CPU context
433 switches and similar is less significant, and it uses the scheduler's own CPU
435 decisions made by the other parts of the scheduler.
453 there if necessary.  As a result, the scheduler context overhead from this
646 scheduler tick interval) and it is demonstrably suitable for many workloads, but