[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bnma6xwv.fsf@x220.int.ebiederm.org>
Date: Wed, 07 Jan 2015 16:14:40 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "Serge E. Hallyn" <serge@...lyn.com>
Cc: Richard Weinberger <richard@....at>,
Linux API <linux-api@...r.kernel.org>,
Linux Containers <containers@...ts.linux-foundation.org>,
Serge Hallyn <serge.hallyn@...ntu.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
Andy Lutomirski <luto@...capital.net>,
Tejun Heo <tj@...nel.org>,
cgroups mailinglist <cgroups@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCHv3 8/8] cgroup: Add documentation for cgroup namespaces
"Serge E. Hallyn" <serge@...lyn.com> writes:
>> By unified hierarchy I mean that every mount of cgroupfs has the
>> same directories with the same processes in each directory.
>
> No, my reading of Documentation/cgroups/unified-hierarchy.txt is that
> unified hierarchy means that all (sane) controllers are co-mounted into
> one hierarchy.
I see what you mean. If it is indeed the case than a mount of cgroupfs
using the unified hiearchy and can not specify which controllers are
present under that mount that very significant bug and presents a very
significant regression in user space flexibility.
I think you can still mount the unified hierarchy and select which
controls you want to see. If you can not that is a change significantly
past what was agreed to and a regression fix needs to be applied.
With a unified hierarchy and separate controllers per mount many cgroup
using applications will continue to work as before without changes, or
with minimal changes. That is what was agreed to and what I expect has
been actually implemented and it is what needs to be implemented in any
case.
I will see about making time to see where things are really at.
Eric
--
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