Nick wrote:
> It is this non overlapping property that we can take advantage of, and
> partition the scheduler.
You want non-overlapping versus all other CPUs on the system.
You want to partition the systems CPUs, in the mathematical sense of
the word 'partition', a non-overlapping cover. Fine. That's an
honorable goal.
But cpu_exclusive gives you non-overlapping versus sibling cpusets.
Wrong tool for the job. Close - sounded right - has that nice long
word 'exclusive' in there somewhere. Wrong one however. It made
good sense to anyone that came at this from the kernel/sched.c side,
as it was obvious to them what was needed. To myself and my cpuset
users, it made no bleeping sense whatsoever.
What actual needs do we have here? Lets figure that out, then if that
leads to adding mechanism of the right shape to fit the needs, fine.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
