Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752481Ab3F0AQj (ORCPT ); Wed, 26 Jun 2013 20:16:39 -0400 Received: from mail.lang.hm ([64.81.33.126]:45048 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750843Ab3F0AQi (ORCPT ); Wed, 26 Jun 2013 20:16:38 -0400 Date: Wed, 26 Jun 2013 16:14:07 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Tim Hockin cc: Tejun Heo , Li Zefan , Containers , Cgroups , bsingharora , "dhaval.giani" , Kay Sievers , jpoimboe , "Daniel P. Berrange" , lpoetter , workman-devel , "linux-kernel@vger.kernel.org" Subject: Re: cgroup: status-quo and userland efforts In-Reply-To: Message-ID: References: <20130406012159.GA17159@mtj.dyndns.org> <20130422214159.GG12543@htj.dyndns.org> <20130625000118.GT1918@mtj.dyndns.org> <20130626212047.GB4536@htj.dyndns.org> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2215 Lines: 53 On Wed, 26 Jun 2013, Tim Hockin wrote: > On Wed, Jun 26, 2013 at 2:20 PM, Tejun Heo wrote: >> Hello, Tim. >> >> On Mon, Jun 24, 2013 at 09:07:47PM -0700, Tim Hockin wrote: >>> I really want to understand why this is SO IMPORTANT that you have to >>> break userspace compatibility? I mean, isn't Linux supposed to be the >>> OS with the stable kernel interface? I've seen Linus rant time and >>> time again about this - why is it OK now? >> >> What the hell are you talking about? Nobody is breaking userland >> interface. A new version of interface is being phased in and the old > > The first assertion, as I understood, was that (eventually) cgroupfs > will not allow split hierarchies - that unified hierarchy would be the > only mode. Is that not the case? > > The second assertion, as I understood, was that (eventually) cgroupfs > would not support granting access to some cgroup control files to > users (through chown/chmod). Is that not the case? As a bystander, what I understand to be happening is: 1. the Kernel developers are saying that multiple hierarchies is causing lots of problems, and so they are starting the migration to a unified hierarchy. In the near term this will be optional, at a later (unspecified) point, it will no longer be optional. It is recognized that this is an API break, but the problem is bad enough (too much undefined behavior) that it looks like they are going to do this anyway. 2. indpendantly from this, the systemd people have declared that systemd is going to take control of this unified hierarchy and all applications had better use DBUS calls to systemd to make any cgroup changes or else. (i.e. systemd may break whatever you are doing) I don't think the kernel developers are talking about changing ways to control cgroups, just eliminating having multiple hierarchies. Now, I could be completely misunderstanding this (and I expect to hear about it if I am :-) David Lang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/