From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759565AbYDJWuU (ORCPT ); Thu, 10 Apr 2008 18:50:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759178AbYDJWuB (ORCPT ); Thu, 10 Apr 2008 18:50:01 -0400 Received: from e36.co.us.ibm.com ([32.97.110.154]:48193 "EHLO e36.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756029AbYDJWuA (ORCPT ); Thu, 10 Apr 2008 18:50:00 -0400 Date: Thu, 10 Apr 2008 17:49:47 -0500 From: "Serge E. Hallyn" To: Daniel Hokka Zakrisson Cc: "Serge E. Hallyn" , Andi Kleen , "David C. Hansen" , linux-kernel@vger.kernel.org, Cedric Le Goater , Containers , Pavel Emelyanov Subject: Re: [PATCH 1/3] change clone_flags type to u64 Message-ID: <20080410224947.GA8346@sergelap.austin.ibm.com> References: <20080409222611.GA28087@us.ibm.com> <20080409223231.GA28267@us.ibm.com> <871w5enmk7.fsf@basil.nowhere.org> <47FE073B.3060007@fr.ibm.com> <20080410125205.GG10019@one.firstfloor.org> <20080410171453.GA7023@sergelap.ibm.com> <49365.192.168.101.12.1207865580.squirrel@intranet> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49365.192.168.101.12.1207865580.squirrel@intranet> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Daniel Hokka Zakrisson (daniel@hozac.com): > Serge E. Hallyn wrote: > > Quoting Andi Kleen (andi@firstfloor.org): > >> > I guess that was a development rationale. > >> > >> But what rationale? It just doesn't make much sense to me. > >> > >> > Most of the namespaces are in > >> > use in the container projects like openvz, vserver and probably others > >> > and we needed a way to activate the code. > >> > >> You could just have added it to feature groups over time. > >> > >> > > >> > Not perfect I agree. > >> > > >> > > With your current strategy are you sure that even 64bit will > >> > > be enough in the end? For me it rather looks like you'll > >> > > go through those quickly too as more and more of the kernel > >> > > is namespaced. > >> > > >> > well, we're reaching the end. I hope ! devpts is in progress and > >> > mq is just waiting for a clone flag. > >> > >> Are you sure? > > > > Well for one thing we can take a somewhat different approach to new > > clone flags. I.e. we could extend CLONE_NEWIPC to do mq instead of > > introducing a new clone flag. The name doesn't have 'sysv' in it, > > and globbing all ipc resources together makes some amount of sense. > > Similarly has hpa+eric pointed out earlier, suka could use > > CLONE_NEWDEV for ptys. If we have net, pid, ipc, devices, that's a > > pretty reasonable split imo. Perhaps we tie user to devices and get > > rid of CLONE_NEWUSER which I suspect noone is using atm (since only > > Dave has run into the CONFIG_USER_SCHED problem). Or not. We could > > roll uts into net, and give CLONE_NEWUTS a deprecation period. > > Please don't. Then we'd need to re-add it in Linux-VServer to support > guests where network namespaces aren't used... So these are networked vservers with a different hostname? Just curious, what would be a typical use for these? Anyway then I guess we won't :) Do you have other suggestions for ns clone flags which ought to be combined? Do the rest of what I listed make sense to you? (If not, then I guess I'll step out of the way and let you and Andi fight it out :) thanks, -serge