[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090116120227.def88bc8.kamezawa.hiroyu@jp.fujitsu.com>
Date: Fri, 16 Jan 2009 12:02:27 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: matthltc@...ibm.com, Paul Menage <menage@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"lizf@...fujitsu.com" <lizf@...fujitsu.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
Containers <containers@...ts.linux-foundation.org>
Subject: Re: [RFC][PATCH] NOOP cgroup subsystem
On Fri, 16 Jan 2009 11:45:02 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote:
> On Thu, 15 Jan 2009 18:20:45 -0800
> Matthew Helsley <matthltc@...ibm.com> wrote:
> I think
> - Paul's suggestion sounds attractive. But I can't see fundamental differences
> from user's side between "implemented as subsys" and "implemetned as cgroup's
> feature". I feel it's easier for user's cgroup library to handle subsys rather
> than "we can mount it anywhere, multiple times!".
> Flexiblity doesn't means it's easy to use.
I should consider more....
mutiple mount point means that the process can belongs to multiple nickname
groups. oh yes, seems worth to try.
Thanks,
-Kame
--
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