Re: [PATCH 1/5] cpuset memory spread basic implementation

[Ingo Molnar]

* Paul Jackson <pj@xxxxxxx> wrote:

> Ingo wrote:
> > Could you perhaps outline two actual use-cases 
> > that would need two cpusets with different policies,
> > on the same box?
> 
> We normally run with different policies, in the same box, on different 
> cpusets at the same time.  But this might be because some cpusets 
> -need- the memory spreading, and the others that don't are left to the 
> default policy.

so in practice, the memory spreading is in fact a global setting, used
by all cpusets that matter? That seems to support Andrew's observation
that our assumptions / defaults are bad, pretty much independently of
the workload.

	Ingo
-
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/