[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130628224310.GF18889@mtj.dyndns.org>
Date: Fri, 28 Jun 2013 15:43:10 -0700
From: Tejun Heo <tj@...nel.org>
To: Serge Hallyn <serge.hallyn@...ntu.com>
Cc: "Daniel P. Berrange" <berrange@...hat.com>,
Vivek Goyal <vgoyal@...hat.com>,
Tim Hockin <thockin@...kin.org>,
Mike Galbraith <bitbucket@...ine.de>,
Containers <containers@...ts.linux-foundation.org>,
Kay Sievers <kay.sievers@...y.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
lpoetter <lpoetter@...hat.com>, Michal Hocko <mhocko@...e.cz>,
"dhaval.giani" <dhaval.giani@...il.com>,
Cgroups <cgroups@...r.kernel.org>,
workman-devel <workman-devel@...hat.com>
Subject: Re: [Workman-devel] cgroup: status-quo and userland efforts
On Fri, Jun 28, 2013 at 05:40:53PM -0500, Serge Hallyn wrote:
> > The kernel can exposed a knob that would allow systemd to lock that
> > down
>
> Gah - why would you give him that idea? :)
That's one of the ideas I had from the beginning.
> But yes, I'd sort of assume that was coming, eventually.
But I think we'll probably settle with a mechanism to find out whether
someone else is touching the hierarchy, which will be generally useful
for other consumers of cgroup too.
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