On Fri, 2014-04-04 at 14:05 +0530, Viresh Kumar wrote:
We need to migrate away all the background kernel activities (Unbound) for systems requiring isolation of cores (HPC, Real time, networking, etc). After creating cpusets, you can write 1 or 0 to cpuset.quiesce file.
I wonder if adding a quiesce switch is really necessary.
Seems to me that if you don't have load balancing turned off, you can't be very concerned about perturbation, so this should be tied into the load balancing on/off switch as an extension to isolating cores from the #1 perturbation source, the scheduler.
I also didn't notice a check for is_cpu_exclusive() at a glance, which would be a bug, but one that would go away if this additional isolation were coupled to the existing isolation switch.
-Mike