Paul Jackson wrote:
Nick wrote:
Or, another question, how does my patch hijack cpus_allowed? In
what way does it change the semantics of cpus_allowed?
It limits load balancing for tasks in cpusets containing
a superset of that cpusets cpus.
There are always such cpusets - the top cpuset if no other.
Ah OK, and there is my misunderstanding with cpusets. From the
documentation it appears as though cpu_exclusive cpusets are
made in order to do the partitioning thing.
If you always have other domains overlapping them (regardless
that it is a parent), then what actual use does cpu_exclusive
flag have?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
-
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]