Lines Matching refs:CPU
5 This document lists per-CPU kthreads in the Linux kernel and presents
6 options to control their OS jitter. Note that non-per-CPU kthreads are
7 not listed here. To reduce OS jitter from non-per-CPU kthreads, bind
8 them to a "housekeeping" CPU dedicated to such work.
23 - /sys/devices/system/cpu/cpuN/online: Control CPU N's hotplug state,
26 - In order to locate kernel-generated OS jitter on CPU N:
46 that does not require per-CPU kthreads. This will prevent these
52 3. Rework the eHCA driver so that its per-CPU kthreads are
65 some other CPU.
78 occur on some other CPU and furthermore initiate all
79 Bluetooth activity on some other CPU.
95 1. To the extent possible, keep the CPU out of the kernel when it
99 the CPU offline, then bring it back online. This forces
113 3. Once your application has started, prevent CPU-hotplug operations
114 from being initiated from tasks that might run on the CPU to
115 be de-jittered. (It is OK to force this CPU offline and then
123 1. Force block-device interrupts onto some other CPU.
125 3. Once your application has started, prevent CPU-hotplug operations
126 from being initiated from tasks that might run on the CPU to
127 be de-jittered. (It is OK to force this CPU offline and then
135 1. Force block-device interrupts onto some other CPU.
137 3. Once your application has started, prevent CPU-hotplug operations
138 from being initiated from tasks that might run on the CPU to
139 be de-jittered. (It is OK to force this CPU offline and then
158 1. Avoid sending scheduler IPIs to the CPU to be de-jittered,
160 on that CPU. If a thread that expects to run on the de-jittered
161 CPU awakens, the scheduler will send an IPI that can result in
163 2. CONFIG_NO_HZ_FULL=y and ensure that the CPU to be de-jittered
164 is marked as an adaptive-ticks CPU using the "nohz_full="
166 interrupts that the de-jittered CPU receives, minimizing its
169 3. To the extent possible, keep the CPU out of the kernel when it
173 received by the de-jittered CPU.
180 1. To the extent possible, keep the CPU out of the kernel when it
184 CPU offline, then bring it back online. This forces recurring
196 1. Offload callbacks and keep the CPU in either dyntick-idle or
199 a. CONFIG_NO_HZ_FULL=y and ensure that the CPU to be
200 de-jittered is marked as an adaptive-ticks CPU using the
203 b. To the extent possible, keep the CPU out of the kernel
212 b. Ensure that the CPU goes idle frequently, allowing other
216 the CPU in question has passed through a quiescent state.
217 c. To the extent possible, keep the CPU out of the kernel
248 use of each CPU's workqueues to run its cache_reap()
252 c. Limit your CPU frequency so that a CPU-frequency
255 correctly, and if you CPU architecture permits, you should
257 avoid the CPU-frequency governor periodically running
258 on each CPU, including cs_dbs_timer() and od_dbs_timer().
260 WARNING: Please check your CPU specifications to
272 but if your workload is CPU-bound, this is a bad idea.
279 daemon from running on each CPU every second or so.
283 WARNING: Please check your CPU specifications to
288 WARNING: Please check your CPU specifications to
291 CONFIG_PMAC_RACKMETER=n to disable the CPU-meter,
315 4. Ensure that the CPU never enters the kernel, and, in particular,
316 avoid initiating any CPU hotplug operations on this CPU. This is
318 CPU, again preventing the rcuc/%u kthreads from having any work
325 Offload RCU callbacks from the corresponding CPU.
330 to execute on some other CPU.