Re: [PATCH 07/41] cpuset: Set up interface for nohz flag
From: Peter Zijlstra
Date: Tue May 08 2012 - 11:48:31 EST
On Tue, 2012-05-08 at 10:38 -0500, Christoph Lameter wrote:
> On Tue, 8 May 2012, Peter Zijlstra wrote:
> > isolating how? The only way to do that is with the (broken) isolcpus
> > crap and cpusets. There is no other way.
> For some reason this seems to work here. What is broken with isolcpus?
It mostly still works I think, but iirc there were a few places that
ignored the cpuisol mask.
But really the moment we get proper means of flushing cpu state
(currently achievable by unplug-replug) isolcpu gets depricated and
cpusets can do what isolcpu can and more (provided this flush thing).
> > Furthermore there is no other partitioning scheme, cpusets is it.
> One can partition the system anyway one wants by setting cpu affinities
> and memory policies etc. No need for cpusets/cgroups.
Not so, the load-balancer will still try to move the tasks and
subsequently fail. Partitioning means it won't even try to move tasks
across the partition boundary.
By proper partitioning you can split load balance domains (or completely
disable the load-balancer by giving it a single cpu domain).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/