From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: [RFC] Network namespaces a path to mergable code. Date: Tue, 27 Jun 2006 11:20:40 -0600 Message-ID: References: <20060626134945.A28942@castle.nmd.msu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dlezcano@fr.ibm.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, serue@us.ibm.com, haveblue@us.ibm.com, clg@fr.ibm.com, Andrew Morton , dev@sw.ru, herbert@13thfloor.at, devel@openvz.org, sam@vilain.net, viro@ftp.linux.org.uk Return-path: Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:31663 "EHLO ebiederm.dsl.xmission.com") by vger.kernel.org with ESMTP id S1161215AbWF0RVu (ORCPT ); Tue, 27 Jun 2006 13:21:50 -0400 To: Andrey Savochkin In-Reply-To: <20060626134945.A28942@castle.nmd.msu.ru> (Andrey Savochkin's message of "Mon, 26 Jun 2006 13:49:45 +0400") Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Thinking about this I am going to suggest a slightly different direction for get a patchset we can merge. First we concentrate on the fundamentals. - How we mark a device as belonging to a specific network namespace. - How we mark a socket as belonging to a specific network namespace. As part of the fundamentals we add a patch to the generic socket code that by default will disable it for protocol families that do not indicate support for handling network namespaces, on a non-default network namespace. I think that gives us a path that will allow us to convert the network stack one protocol family at a time instead of in one big lump. Stubbing off the sysfs and sysctl interfaces in the first round for the non-default namespaces as you have done should be good enough. The reason for the suggestion is that most of the work for the protocol stacks ipv4 ipv6 af_packet af_unix is largely noise, and simple replacement without real design work happening. Mostly it is just tweaking the code to remove global variables, and doing a couple lookups. Eric