From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: Kazunaga Ikeno <k-ikeno@ak.jp.nec.com>,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/1]a new optional function for task assignment to cgroup
Date: Wed, 5 Mar 2008 12:43:38 +0530 [thread overview]
Message-ID: <20080305071338.GA7588@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830803042156y5a28978fi995eb9050f8f5320@mail.gmail.com>
On Tue, Mar 04, 2008 at 09:56:13PM -0800, Paul Menage wrote:
> Hi Kazunaga,
>
> On Tue, Mar 4, 2008 at 9:39 PM, Kazunaga Ikeno <k-ikeno@ak.jp.nec.com> wrote:
> > Hi -
> >
> > This is a patch of a new optional function for task assignment to cgroup, RFC.
> >
> >
> > == Purpose =================================================
> >
> > To provide the function that leads a task, corresponding to the conditions specified
> > beforehand, to a specific cgroup directory.
> >
>
> This is something that's been discussed before, originally as part of
> CKRM with a complex rule engine in the kernel space.
>
> Basically, the general agreement was that it's a case where a simple
> API is going to be too simple for the majority of users, and a complex
> API that satisfies everyone is going to be too messy/heavyweight.
>
> This is something that can be done in a userspace daemon via the
> process events connector - when you get a PROC_EVENT_UID event, you
> can move the process into the appropriate cgroup (you may also need to
> check any recently-forked children). This also gives you more
> flexibility than you can have in the kernel - you can base your
> decision on more complex factors than simply the uid of the process.
>
> Dhaval Giani had a prototype implementation of such a daemon.
>
The daemon was posted at
http://article.gmane.org/gmane.linux.kernel/553267 . At that point
control groups were called containers. These corrections will have to
made for it to run.
If I can get the time, I will clean it up and try to put it up
somewhere.
Thanks,
--
regards,
Dhaval
next prev parent reply other threads:[~2008-03-05 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 5:39 [RFC][PATCH 0/1]a new optional function for task assignment to cgroup Kazunaga Ikeno
[not found] ` <47CE322A.9060907-l0HG/lpvHE58UrSeD/g0lQ@public.gmane.org>
2008-03-05 5:56 ` Paul Menage
2008-03-05 5:56 ` Paul Menage
2008-03-05 7:02 ` Kazunaga Ikeno
2008-03-05 7:05 ` Paul Menage
2008-03-05 7:05 ` Paul Menage
2008-03-05 7:13 ` Dhaval Giani [this message]
[not found] ` <6599ad830803042156y5a28978fi995eb9050f8f5320-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-05 7:02 ` Kazunaga Ikeno
2008-03-05 7:13 ` Dhaval Giani
-- strict thread matches above, loose matches on Subject: below --
2008-03-05 5:39 Kazunaga Ikeno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080305071338.GA7588@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=k-ikeno@ak.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.