Re: scheduler scalability - cgroups, cpusets and load-balancing

Paul Jackson
2008-01-29T20:57:05Z

Gregory wrote:
> By moving it into the root_domain structure, there is now an instance
> per (um, for lack of a better, more up to date word) "exclusive"
> cpuset. That way, disparate cpusets will not bother each other with
> overload notifications, etc.

So the root_domain structure is meant to be the portions of the
sched_domains that are shared across all CPUs in that sched_domain ?

And the word 'cpuset', occurring in the above quote twice, should
be 'sched_domain', right ? Surely these aren't cpuset's ;).

And 'exclusive cpuset' really means 'non-overlapping sched_domain' ?

Or am I still confused ?

I would like to get our concepts clear, and terms consistent. That's
important for those others who would try to understand this.

--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214