Lines Matching full:there

12 There are three main ways of managing scheduling-clock interrupts
38 there are some situations where this old-school approach is still the
40 that use short bursts of CPU, where there are very frequent idle
43 clock interrupts will normally be delivered any way because there
68 If a CPU is idle, there is little point in sending it a scheduling-clock
80 unnecessary scheduling-clock interrupts.  In these situations, there
98 There is also a boot parameter "nohz=" that can be used to disable
107 If a CPU has only one runnable task, there is little point in sending it
108 a scheduling-clock interrupt because there is no other task to switch to.
121 by one less than the number of CPUs.  In these situations, there is
131 (This is not an issue for CONFIG_NO_HZ_IDLE=y because there are no running
163 4.	If there are more perf events pending than the hardware can
183 There are situations in which idle CPUs cannot be permitted to
263 *	Adaptive-ticks does not do anything unless there is only one
264 	runnable task for a given CPU, even though there are a number
271 	this CPU, so there is no point in sending a scheduling-clock
277 	And even when there are multiple runnable tasks on a given CPU,
278 	there is little point in interrupting that CPU until the current
287 	runtime, there would need to be an earthshakingly good reason.
312 *	If there might potentially be some adaptive-ticks CPUs, there