Messages in this thread | | | Date | Wed, 20 Sep 2006 17:34:52 -0700 | From | "Paul Menage" <> | Subject | Re: [ckrm-tech] [patch00/05]: Containers(V2)- Introduction |
| |
On 9/20/06, Chandra Seetharaman <sekharan@us.ibm.com> wrote: > > What I am wondering is that whether the tight coupling of rg and cpuset > (into a container data structure) is ok.
Can you suggest a realistic scenario in which it's not? Don't forget that since the container abstraction is hierarchical, you don't have to use both at the same level. So you could easily e.g. have a parent container in which you bound to a set of memory/cpu nodes, but had no rg limits, and several subcontainers where you configured nothing special for cpuset parameters (so inherited the parent params) but tweaked different rg parameters.
Paul - 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/
| |