Lines Matching full:cpus

19 2.	Omit scheduling-clock ticks on idle CPUs (CONFIG_NO_HZ_IDLE=y or
23 3.	Omit scheduling-clock ticks on CPUs that are either idle or that
65 Omit Scheduling-Clock Ticks For Idle CPUs
78 scheduling-clock interrupts to idle CPUs, which is critically important
86 idle CPUs.  That said, dyntick-idle mode is not free:
104 Omit Scheduling-Clock Ticks For CPUs With Only One Runnable Task
109 Note that omitting scheduling-clock ticks for CPUs with only one runnable
110 task implies also omitting them for idle CPUs.
113 sending scheduling-clock interrupts to CPUs with a single runnable task,
114 and such CPUs are said to be "adaptive-ticks CPUs".  This is important
119 delayed during a given iteration, all the other CPUs will be forced to
121 by one less than the number of CPUs.  In these situations, there is
125 boot parameter specifies the adaptive-ticks CPUs.  For example,
126 "nohz_full=1,6-8" says that CPUs 1, 6, 7, and 8 are to be adaptive-ticks
127 CPUs.  Note that you are prohibited from marking all of the CPUs as
128 adaptive-tick CPUs:  At least one non-adaptive-tick CPU must remain
130 calls like gettimeofday() returns accurate values on adaptive-tick CPUs.
133 means that your system must have at least two CPUs in order for
136 Finally, adaptive-ticks CPUs must have their RCU callbacks offloaded.
156 3.	POSIX CPU timers prevent CPUs from entering adaptive-tick mode.
164 	preventing CPUs with large numbers of perf events pending from
167 5.	Scheduler statistics for adaptive-tick CPUs may be computed
168 	slightly differently than those for non-adaptive-tick CPUs.
180 There are situations in which idle CPUs cannot be permitted to
185 using the CONFIG_RCU_NOCB_CPU=y Kconfig option.  The specific CPUs to
187 which takes a comma-separated list of CPUs and CPU ranges, for example,
188 "1,3-5" selects CPUs 1, 3, 4, and 5.  Note that CPUs specified by
191 The offloaded CPUs will never queue RCU callbacks, and therefore RCU
192 never prevents offloaded CPUs from entering either dyntick-idle mode
194 pin the "rcuo" kthreads to specific CPUs if desired.  Otherwise, the
218 Note: this test requires that your system have at least two CPUs.
248 		CPUs, which can significantly reduce maximum performance.
266 	nevertheless sends scheduling-clock interrupts to CPUs having a
282 	simply offloading RCU callbacks from all CPUs and pinning them
288 	interrupts and tasks to particular CPUs.
301 *	Unless all CPUs are idle, at least one CPU must keep the
305 *	If there might potentially be some adaptive-ticks CPUs, there
307 	going, even if all CPUs are otherwise idle.