From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 0/9] Multiple devpts instances Date: Mon, 23 Feb 2009 13:23:52 -0800 Message-ID: <49A313E8.1020309@zytor.com> References: <20081015053000.GA2039@us.ibm.com> <499D7E13.10601@free.fr> <499D97B1.1090902@zytor.com> <499DA069.3040603@free.fr> <499DB9DA.2070301@zytor.com> <499DE06E.4030108@free.fr> <20090223205609.GA32351@us.ibm.com> <49A312E6.9090900@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49A312E6.9090900-GANU6spQydw@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Daniel Lezcano Cc: kyle-hoO6YkzgTuCM0SS3m2neIg@public.gmane.org, "David C. Hansen" , bastian-yyjItF7Rl6lg9hUCZPvPmw@public.gmane.org, "Eric W. Biederman" , containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org, sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org, alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org, xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org List-Id: containers.vger.kernel.org Daniel Lezcano wrote: > > Yep, I changed my mind, I think Eric and HPA are right. devpts is a > file system and not a namespace even if the result is the same. That > makes sense to keep a global sysctl for the root container and handle > security problem with user namespace and mount option. > No, it's more dramatic than that. Namespaces are not resource allocation boundaries, even though in the container use case you probably want both. Furthermore, namespaces are relatively straightforward in comparison: you generally either want to share a namespace or you don't. Resource control policies are much more complex. In the general case you want to be able to support a hierarchial cascade of policies; at the least you want to have global and local limits. Furthermore, there are a number of use cases for resource allocation boundaries that do *not* involve namespaces. -hpa