[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F5F1D67.10001@parallels.com>
Date: Tue, 13 Mar 2012 14:11:51 +0400
From: Glauber Costa <glommer@...allels.com>
To: Peter Zijlstra <peterz@...radead.org>
CC: Tejun Heo <tj@...nel.org>, 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>,
Lennart Poettering <lennart@...ttering.net>,
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
On 03/13/2012 02:44 AM, Peter Zijlstra wrote:
> On Mon, 2012-03-12 at 15:39 -0700, Tejun Heo wrote:
>> > If we can get to the point where nesting is fully
>> > supported by every controller first, that would be awesome too.
> As long as that is the goal.. otherwise, I'd be overjoyed if I can rip
> nesting support out of the cpu-controller.. that stuff is such a pain.
> Then again, I don't think the container people like this proposal --
> they were the ones pushing for full hierarchy back when.
Indeed. At some point it is desirable that an admin inside the container
be able to divide resources between the tasks they see.
Maybe it doesn't even make sense for things like I/O, for each he at
most has an illusion of control anyway. But cpu is a lot more tangible
resource in this regard.
--
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