[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080710171939.GB12043@redhat.com>
Date: Thu, 10 Jul 2008 13:19:39 -0400
From: Vivek Goyal <vgoyal@...hat.com>
To: Paul Menage <menage@...gle.com>
Cc: linux kernel mailing list <linux-kernel@...r.kernel.org>,
Libcg Devel Mailing List <libcg-devel@...ts.sourceforge.net>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
Peter Zijlstra <pzijlstr@...hat.com>,
kamezawa.hiroyu@...fujitsu.com,
Kazunaga Ikeno <k-ikeno@...jp.nec.com>,
Morton Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC] How to handle the rules engine for cgroups
On Thu, Jul 10, 2008 at 09:41:06AM -0700, Paul Menage wrote:
> On Thu, Jul 10, 2008 at 7:06 AM, Vivek Goyal <vgoyal@...hat.com> wrote:
> >
> > This looks interesting. So above method should solve atleast the
> > reliability issue of event transport to user space. Got few thougts.
> >
> > - Hopefully number of hiearchies will not explode as we will be
> > mounting one hierarchies per event type (uid change, gid change,
> > exec, maybe fork etc.).
>
> In what circumstances would you want to reclassify processes to a
> different cgroup on a fork?
I don't know. Balbir had mentioned in one of the mails in this thread
regarding getting notification on fork.
Thanks
Vivek
--
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