Re: [PATCH 08/32] nohz: Try not to give the timekeeping duty to anadaptive tickless cpu

From: Frederic Weisbecker
Date: Tue Mar 27 2012 - 06:50:40 EST

On Wed, Mar 21, 2012 at 09:52:24AM -0500, Christoph Lameter wrote:
> On Wed, 21 Mar 2012, Frederic Weisbecker wrote:
> > Try to give the timekeeing duty to a CPU that doesn't belong
> > to any nohz cpuset when possible, so that we increase the chance
> > for these nohz cpusets to run their CPUs out of periodic tick
> > mode.
> Any way to manually specify which cpu? We f.e. always "sacrifice" cpu 0
> for OS activities. We would like to have all Os processing things
> restricted to cpu 0 so that the rest of the processors do not experience
> the OS noise.

Somebody tries to do this:

But in the case of nohz cpusets there is a problem to solve:

What if every CPUs are tickless (idle or busy), who must take
the timekeeping duty? Should we pick one of the busy CPUs? Or
keep one CPU with the tick even if it's idle? How do we choose
this CPU?

May be we need to define another flag on cpusets to assign the
timekeeping duty to any CPU on a flagged set. This way we can
force that duty to the CPU(s) we want.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at