[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130409211152.GO6186@mtj.dyndns.org>
Date: Tue, 9 Apr 2013 14:11:52 -0700
From: Tejun Heo <tj@...nel.org>
To: Serge Hallyn <serge.hallyn@...ntu.com>
Cc: "Daniel P. Berrange" <berrange@...hat.com>, jpoimboe@...hat.com,
linux-kernel@...r.kernel.org,
containers@...ts.linux-foundation.org,
Kay Sievers <kay.sievers@...y.org>, lpoetter@...hat.com,
workman-devel@...hat.com, dhaval.giani@...il.com,
cgroups@...r.kernel.org
Subject: Re: cgroup: status-quo and userland efforts
Hey, Serge.
On Tue, Apr 09, 2013 at 04:04:22PM -0500, Serge Hallyn wrote:
> So for instance if there is a dbus call saying "please create cgroup
> /x with (some constraints) and put $$ into it", "something" in the
> container can convert that into "please create cgroup /lxc/c1/x
> and put (host_uid($$)) into it" and pass that to the host's (or
> parent container's) "something".
Yeap, definitely. It shouldn't be difficult to make it transparent to
individual consumers. It would actually be far easier to achieve that
with userland agent which knows what's going on in the middle.
> So perhaps it is best if the container monitor, living in the parent
> namespaces, opens a socket '@...oup_monitor' in the container
> namespace (through setns), listens for container-userpsace requests
> there, and passes them on to the host's monitor (which hopefully
> also listens on '@...oup_monitor', @ being '\0'). Note that my
> mentino of converting pids requires a new kernel feature which we
> don't currently have (but have wanted for a long time).
Yeah, details may change but in principle something like that.
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