Messages in this thread | | | Date | Mon, 4 Jun 2007 12:31:51 -0700 | From | Paul Jackson <> | Subject | Re: [PATCH 00/10] Containers(V10): Generic Process Containers |
| |
What you describe, Serge, sounds like semantics carried over from cpusets.
Serge wrote: > A task can't join a cpuset unless 'cpus' and 'mems' are set.
Yup - don't want to run a task in a cpuset that lacks cpu, or lacks memory. Hard to run without those.
> These don't seem to automatically inherit the parent's values
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.
So we changed it to creating new cpusets empty of cpus or memory.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.925.600.0401 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |