> If you always have other domains overlapping them (regardless
> that it is a parent), then what actual use does cpu_exclusive
> flag have?
Good question. To be a tad too honest, I don't consider it to be
all that essential.
It does turn out to be a bit useful, in that you can be confident that
if you are administering the batch scheduler and it has a cpu_exclusive
cpuset covering a big chunk of your system, then no other cpuset other
than the top cpuset right above, which you administer pretty tightly,
could have anything overlapping it. You don't have to actually look
at the cpumasks in all the parallel cpusets and cross check each one
against the batch schedulers set of cpus for overlap.
But as you can see by grep'ing in kernel/cpuset.c, it is only used
to generate a couple of error returns, for things that you can do
just fine by turning off the cpu_exclusive flag.
--
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]
