From mboxrd@z Thu Jan 1 00:00:00 1970 From: Glauber Costa Subject: Re: containers and cgroups mini-summit @ Linux Plumbers Date: Wed, 25 Jul 2012 14:00:41 +0400 Message-ID: <500FC3C9.4010005@parallels.com> References: <4FFDF321.4030103@openvz.org> <500FB473.3090606@parallels.com> <871uk0b1p4.fsf@xmission.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <871uk0b1p4.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org> Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: "Eric W. Biederman" Cc: Kir Kolyshkin , Serge Hallyn , Frederic Weisbecker , Daniel Lezcano , Johannes Weiner , Tejun Heo , Rohit Seth , Greg Thelen , Balbir Singh , Dhaval Giani , KAMEZAWA Hiroyuki , Paul Turner , Tim Hockin , Suleiman Souhlal , Dave Kleikamp , cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org, James Bottomley , Pavel Emelyanov , Maxim Patlasov On 07/25/2012 02:00 PM, Eric W. Biederman wrote: > Glauber Costa writes: > >> On 07/12/2012 01:41 AM, Kir Kolyshkin wrote: >>> Gentlemen, >>> >>> We are organizing containers mini-summit during next Linux Plumbers (San >>> Diego, August 29-31). >>> The idea is to gather and discuss everything relevant to namespaces, >>> cgroups, resource management, >>> checkpoint-restore and so on. >>> >>> We are trying to come up with a list of topics to discuss, so please >>> reply with topic suggestions, and >>> let me know if you are going to come. >>> >>> I probably forgot a few more people (such as, I am not sure who else >>> from Google is working >>> on cgroups stuff), so fill free to forward this to anyone you believe >>> should go, >>> or just let me know whom I missed. >>> >>> Regards, >>> Kir. >> >> BTW, sorry for not replying before (vacations + post-vacations laziness) >> >> I would be interested in adding /proc virtualization to the discussion. >> By now it seems userspace would be the best place for that to happen, in >> a fuse overlay. I know Daniel has an initial implementation of that, and >> it would be good to have it as library that both OpenVZ and LXC (and >> whoever else wants) can use. >> >> Shouldn't take much time... > > What would you need proc virtualization for? > proc provides a lot of information that userspace tools rely upon. For instance, when running top, you can draw per-process figures from what we have now, but you can't make sense of percentages without aggregating container-wide information. When you read /proc/cpuinfo, as well, you would expect to see something that matches your container configuration. "free" is another example. The list go on.