[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120312230949.GN23255@google.com>
Date: Mon, 12 Mar 2012 16:09:49 -0700
From: Tejun Heo <tj@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Lennart Poettering <mzxreary@...inter.de>,
Li Zefan <lizf@...fujitsu.com>,
containers@...ts.linux-foundation.org, cgroups@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Kay Sievers <kay.sievers@...y.org>,
Frederic Weisbecker <fweisbec@...il.com>,
linux-kernel@...r.kernel.org, Vivek Goyal <vgoyal@...hat.com>,
Michal Schmidt <mschmidt@...hat.com>
Subject: Re: [RFD] cgroup: about multiple hierarchies
Hello, Peter.
On Tue, Mar 13, 2012 at 12:02:47AM +0100, Peter Zijlstra wrote:
> On Mon, 2012-03-12 at 16:00 -0700, Tejun Heo wrote:
> >
> > Ooh, both will be available to choose from. I was trying to explain
> > that there can be configuration only at one layer for any task so that
> > it can be mapped to flat hierarchy. Where to apply the config will be
> > selected by the user (or system tool).
>
> Thus in effect this is a false choice, since Lennart and assorted idiots
> conspire against sanity by pushing systemd into our every orifice, and
> since he just said systemd requires one of the two, the choice will be
> made for us, lest we forfeit wanting to boot our system.
I think it should be fine as long as systemd or whatever system cgroup
manager can be told to stay aside about limits. Everyone doing their
own thing and ending up competing directly under /sys/fs/cgroup/
worries me more. cgroup config fs doesn't have enough flexibility or
proper provisions for sharing while encouraging direct usage. That's
not a good combination.
Thanks.
--
tejun
--
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