[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54F13446.8090808@huawei.com>
Date: Sat, 28 Feb 2015 11:21:42 +0800
From: Zefan Li <lizefan@...wei.com>
To: <riel@...hat.com>
CC: <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Clark Williams <williams@...hat.com>,
Ingo Molnar <mingo@...hat.com>,
"Luiz Capitulino" <lcapitulino@...hat.com>,
Mike Galbraith <umgwanakikbuti@...il.com>,
<cgroups@...r.kernel.org>
Subject: Re: [PATCH 1/2] cpusets,isolcpus: exclude isolcpus from load balancing
in cpusets
On 2015/2/26 0:38, riel@...hat.com wrote:
> From: Rik van Riel <riel@...hat.com>
>
> 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.
>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Cc: Clark Williams <williams@...hat.com>
> Cc: Li Zefan <lizefan@...wei.com>
> Cc: Ingo Molnar <mingo@...hat.com>
> Cc: Luiz Capitulino <lcapitulino@...hat.com>
> Cc: Mike Galbraith <umgwanakikbuti@...il.com>
> Cc: cgroups@...r.kernel.org
> Signed-off-by: Rik van Riel <riel@...hat.com>
> Tested-by: David Rientjes <rientjes@...gle.com>
Acked-by: Zefan Li <lizefan@...wei.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists