Nick wrote:
quoted text
> There won't be any CPU cycles used, if the tasks are paused (surely
> they're not spin waiting).

Consider the case when there are two, smaller, non-overlapping cpusets
with active jobs, and one larger cpuset, covering both those smaller
ones, with only paused tasks.

If we realize we don't need to balance the larger cpuset, then we can
have two smaller sched domains rather than one larger one.

Since the CPU cycle cost of load balancing increases more than linearly
with the size of the sched domain, therefore it will save CPU cycles to
have the two smaller ones, rather than the one larger one.

If user space can just tell us that the larger cpuset doesn't need
balancing, then the kernel has enough information to perform this
optimization.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/