Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932073AbWBHDym (ORCPT ); Tue, 7 Feb 2006 22:54:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932172AbWBHDym (ORCPT ); Tue, 7 Feb 2006 22:54:42 -0500 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:24213 "EHLO ebiederm.dsl.xmission.com") by vger.kernel.org with ESMTP id S932073AbWBHDyl (ORCPT ); Tue, 7 Feb 2006 22:54:41 -0500 To: "Serge E. Hallyn" Cc: Alexey Kuznetsov , Hubertus Franke , Sam Vilain , Rik van Riel , Kirill Korotaev , Linus Torvalds , Andrew Morton , linux-kernel@vger.kernel.org, clg@fr.ibm.com, haveblue@us.ibm.com, greg@kroah.com, alan@lxorguk.ukuu.org.uk, arjan@infradead.org, saw@sawoct.com, devel@openvz.org, Dmitry Mishin , Andi Kleen , Herbert Poetzl Subject: Re: The issues for agreeing on a virtualization/namespaces implementation. References: <43E83E8A.1040704@vilain.net> <43E8D160.4040803@watson.ibm.com> <20060207201908.GJ6931@sergelap.austin.ibm.com> <43E90716.4020208@watson.ibm.com> <43E92EDC.8040603@watson.ibm.com> <20060208004325.GA15061@ms2.inr.ac.ru> <20060208033633.GA8784@sergelap.austin.ibm.com> From: ebiederm@xmission.com (Eric W. Biederman) Date: Tue, 07 Feb 2006 20:52:15 -0700 In-Reply-To: <20060208033633.GA8784@sergelap.austin.ibm.com> (Serge E. Hallyn's message of "Tue, 7 Feb 2006 21:36:33 -0600") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1035 Lines: 25 "Serge E. Hallyn" writes: > > What I tried to do in a proof of concept long ago was to have > CLONE_NETNS mean that you get access to all the network devices, but > then you could drop/add them. Conceptually I prefer that to getting an > empty namespace, but I'm not sure whether there's any practical use > where you'd want that... My observation was that the network stack does not come out cleanly as a namespace unless you adopt the rule that a network device belongs to exactly one network namespace. With that rule dealing with the network stack is just a matter of making some currently global variables/data structures per container. A pain to do the first round but easy to maintain once you are there and the logic of the code doesn't need to change. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/