Quoting Paul Menage ([email protected]):
> On 6/4/07, Paul Jackson <[email protected]> wrote:
> >
> >Yup - early in the life of cpusets, a created cpuset inherited the cpus
> >and mems of its parent. But that broke the exclusive property big
> >time. You will recall that a cpu_exclusive or mem_exclusive cpuset
> >cannot overlap the cpus or memory, respectively, of any of its sibling
> >cpusets.
> >
>
> Maybe we could make it a per-cpuset option whether children should
> inherit mems/cpus or not?
The values can be changed after the cpuset is populated, right? So
really these are just defaults? Would it then make sense to just
default to (parent_set - sibling_exclusive_set) for a new sibling's
value?
An option is fine with me, but without such an option at all, cpusets
could not be applied to namespaces...
thanks,
-serge
-
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]
