Messages in this thread | | | Date | Thu, 19 Mar 2015 14:30:01 -0400 | From | Tejun Heo <> | Subject | Re: [PATCH v4 RESEND 0/4] cpusets,isolcpus: exclude isolcpus from load balancing in cpusets |
| |
On Mon, Mar 09, 2015 at 12:12:06PM -0400, riel@redhat.com wrote: > Ensure that cpus specified with the isolcpus= boot commandline > option stay outside of the load balancing in the kernel scheduler. > > Operations like load balancing can introduce unwanted latencies, > which is exactly what the isolcpus= commandline is there to prevent. > > Previously, simply creating a new cpuset, without even touching the > cpuset.cpus field inside the new cpuset, would undo the effects of > isolcpus=, by creating a scheduler domain spanning the whole system, > and setting up load balancing inside that domain. The cpuset root > cpuset.cpus file is read-only, so there was not even a way to undo > that effect. > > This does not impact the majority of cpusets users, since isolcpus= > is a fairly specialized feature used for realtime purposes. > > This version fixes the UP compilation issue, in the same way done > for the other cpumasks.
Applied 1, 2, and 4 to cgroup/for-4.1. I collected the acks from the previous threads. Can you please collect them when posting new revisions in the future?
Thanks.
-- tejun
| |