Lines Matching refs:CPU

37 that use short bursts of CPU, where there are very frequent idle
41 will frequently be multiple runnable tasks per CPU.  In these cases,
64 If a CPU is idle, there is little point in sending it a scheduling-clock
66 is to force a busy CPU to shift its attention among multiple duties,
67 and an idle CPU has no duties to shift its attention among.
75 1,500 OS instances might find that half of its CPU time was consumed by
90 An idle CPU that is not receiving scheduling-clock interrupts is said to
102 If a CPU has only one runnable task, there is little point in sending it
113 computationally intensive short-iteration workloads:  If any CPU is
115 wait idle while the delayed CPU finishes.  Thus, the delay is multiplied
119 By default, no CPU will be an adaptive-ticks CPU.  The "nohz_full="
123 adaptive-tick CPUs:  At least one non-adaptive-tick CPU must remain
128 boot CPU is prohibited from entering adaptive-ticks mode.  Specifying a
129 "nohz_full=" mask that includes the boot CPU will result in a boot-time
130 error message, and the boot CPU will be removed from the mask.  Note that
135 that all CPUs other than the boot CPU are adaptive-ticks CPUs.  This
139 prevail so that only CPU 1 will be an adaptive-ticks CPU.
144 Normally, a CPU remains in adaptive-ticks mode as long as possible.
146 the mode.  Instead, the CPU will exit adaptive-ticks mode only if needed,
147 for example, if that CPU enqueues an RCU callback.
161 3.	POSIX CPU timers prevent CPUs from entering adaptive-tick mode.
162 	Real-time applications needing to take actions based on CPU time
188 common being when that CPU has RCU callbacks pending.
206 		CPU 0 to be offloaded.
211 		will in fact run on some CPU.  However, this approach
218 	list of CPUs and CPU ranges, for example, "1,3-5" selects CPUs 1,
251 We do not currently have a good way to remove OS jitter from single-CPU
275 		your CPU to overheat, which may cause thermal throttling
288 	runnable task for a given CPU, even though there are a number
290 	needed.  To give but one example, consider a CPU that has one
292 	of low-priority SCHED_OTHER tasks.  In this case, the CPU is
295 	this CPU, so there is no point in sending a scheduling-clock
296 	interrupt to this CPU.	However, the current implementation
301 	And even when there are multiple runnable tasks on a given CPU,
302 	there is little point in interrupting that CPU until the current
332 o	Unless all CPUs are idle, at least one CPU must keep the
337 	will be at least one CPU keeping the scheduling-clock interrupt
343 	scheduling-clock tick.	These operations include calculating CPU