![]() | |||||||||||||
Messages in this thread |
Nick wrote:
> Well, it was supposed to be used for sched-domains partitioning, and
> its uselessness for anything else I guess is what threw me.
The use of cpu_exclusive for sched domain partitioning was added
later, by a patch from Dinikar, in April or May of 2005.
In hindsight, I think I made a mistake in agreeing to, and probably
encouraging, this particular overloading of cpu_exclusive. I had
difficulty adequately understanding what was going on.
Granted, as we've noted elsewhere on this thread, the cpu_exclusive
flag is underutilized. It gives cpusets so marked a certain limited
exclusivity to its cpus, relative to its siblings, but it doesn't do
much else, other than this controversial partitioning of sched domains.
There may well be a useful role for the cpu_exclusive flag in managing
sched domains and partitioning. The current role is flawed, in my view.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
-
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/
| ||||||||||||
| Last update: 2006-10-22 06:57 [from the cache] ©2003-2008 | |||||||||||||