Lines Matching refs:that

4 options to control their OS jitter.  Note that non-per-CPU kthreads are
39 	that does not require per-CPU kthreads.  This will prevent these
45 3.	Rework the eHCA driver so that its per-CPU kthreads are
83 	from being initiated from tasks that might run on the CPU to
90 	from being initiated from tasks that might run on the CPU to
97 	from being initiated from tasks that might run on the CPU to
101 1.	Avoid use of drivers that use tasklets.  (Such drivers will contain
103 2.	Convert all drivers that you must use from tasklets to workqueues.
108 	for example, ensure that at most one runnable kthread is present
109 	on that CPU.  If a thread that expects to run on the de-jittered
110 	CPU awakens, the scheduler will send an IPI that can result in
113 	CONFIG_NO_HZ_FULL=y, and, in addition, ensure that the CPU
116 	scheduler-clock interrupts that the de-jittered CPU receives,
118 	work that runs in SCHED_SOFTIRQ context.
139 		CONFIG_NO_HZ_FULL=y, and, in addition ensure that the CPU
150 	b.	Ensure that the CPU goes idle frequently, allowing other
151 		CPUs to detect that it has passed through an RCU quiescent
153 		userspace execution also allows other CPUs to detect that
166 	by passing the WQ_SYSFS to that workqueue's alloc_workqueue().
173 	caution is that it is easy to add WQ_SYSFS, but because sysfs is
176 3.	Do any of the following needed to avoid jitter that your
184 	c.	Limit your CPU frequency so that a CPU-frequency
192 		make sure that this is safe on your particular system.
205 		(based on an earlier one from Gilad Ben-Yossef) that
217 		make sure that this is safe on your particular system.
222 		make sure that this is safe on your particular system.
233 	for workloads that do not require high degrees of responsiveness.
238 	CPUs that might execute within the kernel.
240 	which offloads all RCU callbacks to kthreads that can be moved
242 	rcuc/%u kthreads from having any work to do, so that they are
244 4.	Ensure that the CPU never enters the kernel, and, in particular,
257 	note that this will not eliminate OS jitter, but will instead
273 	timer down to a level that is acceptable for your workload.