Dinakar wrote:
> IMO this change is counter intuitive and pointless
If we intend to make the cpuset to sched_domain interaction
functional, something like this was needed.
However I am now leaning toward thinking that the entire
effort to manipulate sched_domain definitions by cpusets
(the cpu_exclusive flag) has been counter intuitive, and
is borked.
So I will be sending out patches to remove it, and replace
with a trivial mechanism to allow for runtime manipulation
of the cpu_isolated_map.
Coming soon ...
--
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]
