[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070220233222.GB7888@sergelap.austin.ibm.com>
Date: Tue, 20 Feb 2007 17:32:22 -0600
From: "Serge E. Hallyn" <serue@...ibm.com>
To: Paul Menage <menage@...gle.com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Sam Vilain <sam@...ain.net>, akpm@...l.org, pj@....com,
sekharan@...ibm.com, dev@...ru, xemul@...ru, serue@...ibm.com,
vatsa@...ibm.com, containers@...ts.osdl.org, winget@...gle.com,
rohitseth@...gle.com, ckrm-tech@...ts.sourceforge.net,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] containers (V7): Generic Process Containers
Quoting Paul Menage (menage@...gle.com):
> On 2/20/07, Eric W. Biederman <ebiederm@...ssion.com> wrote:
> >All that is necessary to have a group of processes do something
> >in an unnamed fashion is to hang a pointer off of the task_struct.
> >That's easy.
>
> Right, adding a pointer to task_struct is easy. Configuring how/when
> to not directly inherit it from the parent, or to change it for a
> running task, or configuring state associated with the thing that the
> pointer is pointing to, naming that group, and determining which group
> a given process is assocaited with, is something that's effectively
> repeated boiler plate for each different subsystem, and which can be
> accomplished more generically via an abstraction like my containers
> patch.
Eric,
what you gain with this patchset is, one very simple container subsystem
can tie a container to a cpu, another can limit it's RSS, and suddenly
you can
mount -t container -o ns,rss,cpuwhatever ns /container
And each virtual server you create by unsharing can get automatic cpu
and rss controls.
That is worthwhile imo.
-serge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists