Lines Matching refs:CPU
104 * equivalent of some underlying %CPU duty cycle.
106 * awakened every 25 clock ticks. So, converting from %CPU to ticks
173 * timed out (exceeded its CPU budget), rather than because it visited
338 * could lead to thrashing and higher CPU usage.
342 * time for scanning on slow CPU's and avoid thrashing, as a
343 * result of scanning too many pages, on faster CPU's.
347 * of the CPU) on some of the following machines that currently
368 * limited to using ~4% of the CPU. This results in increasing
400 * the fact that user processes running on other CPU's can be
403 * more than one CPU to run the clock algorithm in such a manner
447 * Since pageout is limited to ~4% of the CPU, setting handspreadpages
795 CPU_STATS_ADDQ(CPU, vm, pgrrun, 1);
829 * Check to see if we have exceeded our %CPU budget
855 CPU_STATS_ADDQ(CPU, vm, scan, 1);
878 CPU_STATS_ADDQ(CPU, vm, rev, 1);