Re: [lxc-devel] cgroup management daemon

2013-11-26 Thread Victor Marmol
On Tue, Nov 26, 2013 at 8:12 AM, Serge E. Hallyn se...@hallyn.com wrote: Quoting Tim Hockin (thoc...@google.com): What are the requirements/goals around performance and concurrency? Do you expect this to be a single-threaded thing, or can we handle some number of concurrent operations? Do

Re: [lxc-devel] cgroup management daemon

2013-11-26 Thread Victor Marmol
On Tue, Nov 26, 2013 at 8:41 AM, Serge E. Hallyn se...@hallyn.com wrote: Quoting Victor Marmol (vmar...@google.com): On Tue, Nov 26, 2013 at 8:12 AM, Serge E. Hallyn se...@hallyn.com wrote: Quoting Tim Hockin (thoc...@google.com): What are the requirements/goals around performance

Re: [lxc-devel] cgroup management daemon

2013-11-26 Thread Victor Marmol
I think most of our usecases have only wanted to know about the parent, but I can see people wanting to go further. Would it be much different to support both? I feel like it'll be simpler to support all if we go that route. On Tue, Nov 26, 2013 at 1:28 PM, Serge E. Hallyn se...@hallyn.com

Re: [lxc-devel] cgroup management daemon

2013-12-03 Thread Victor Marmol
I thought we were going to use chown in the initial version to enforce the ownership/permissions on the hierarchy. Only the cgroup manager has access to the hierarchy, but it tries to access the hierarchy as the user that sent the request. It was only meant to be a for now solution while the real