Re: [PATCH 07/41] cpuset: Set up interface for nohz flag
From: Christoph Lameter
Date: Wed May 09 2012 - 10:22:24 EST
On Wed, 9 May 2012, Mike Galbraith wrote:
> > Its not a good match for this. You would want a per cpu attribute for
> > nohz.
> Or per cpuset, which can be the same thing as per cpu if you want.
But now we start to manage per cpu characteristics with cpusets whereas
before cpusets was used mainly to manage groups of processors assigned to
applications! This means there will be a requirement to use cpusets in
environments that have not used them before.
> > isolcpus are not part of load balancer domains.
> Yup, so if you have an application with an RT component, somewhat
> sensitive, needs isolation from rest of a big box, but app also has
> SCHED_OTHER components. isolcpus is a pain, everything has to be static
> and nailed to the floor. Load just works when plugged into a cpuset.
Well you have low latency requirements. If you code for lowest latency
then you have to consider cache sizes, cache sharing etc etc. This means
you will have to nail down everything anyways. Cpusets would just be
another thing that one has to worry about.
The loads definitely wont work right if just "plugged into a cpuset".
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/