Lines Matching full:scheduling

2 NO_HZ: Reducing Scheduling-Clock Ticks
7 reduce the number of scheduling-clock interrupts, thereby improving energy
12 There are three main ways of managing scheduling-clock interrupts
13 (also known as "scheduling-clock ticks" or simply "ticks"):
15 1. Never omit scheduling-clock ticks (CONFIG_HZ_PERIODIC=y or
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
33 Never Omit Scheduling-Clock Ticks
37 are incapable of omitting scheduling-clock ticks. It turns out that
42 hundreds of microseconds). For these types of workloads, scheduling
45 attempting to turn off the scheduling clock interrupt will have no effect
53 periods, failing to omit scheduling-clock interrupts will result in
60 workload with short iterations, the scheduling-clock interrupts can
65 Omit Scheduling-Clock Ticks For Idle CPUs
68 If a CPU is idle, there is little point in sending it a scheduling-clock
69 interrupt. After all, the primary purpose of a scheduling-clock interrupt
73 An idle CPU that is not receiving scheduling-clock interrupts is said to
78 scheduling-clock interrupts to idle CPUs, which is critically important
84 unnecessary scheduling-clock interrupts. In these situations, there
85 is strong motivation to avoid sending scheduling-clock interrupts to
104 Omit Scheduling-Clock Ticks For CPUs With Only One Runnable Task
108 a scheduling-clock interrupt because there is no other task to switch to.
109 Note that omitting scheduling-clock ticks for CPUs with only one runnable
113 sending scheduling-clock interrupts to CPUs with a single runnable task,
117 duration of a scheduling-clock interrupt. It is also important for
122 again strong motivation to avoid sending scheduling-clock interrupts.
231 eliminate scheduling-clock interrupt latencies. Here are some
258 of other situations where the scheduling-clock tick is not
264 this CPU, so there is no point in sending a scheduling-clock
266 nevertheless sends scheduling-clock interrupts to CPUs having a
273 longer than the time of the next scheduling-clock interrupt.
302 scheduling-clock interrupt going in order to support accurate
306 will be at least one CPU keeping the scheduling-clock interrupt
312 scheduling-clock tick. These operations include calculating CPU
315 currently accommodated by scheduling-clock tick every second
317 infrequent scheduling-clock ticks.