From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: [PATCH 7/8] net: Allow setting the network namespace by fd Date: Thu, 23 Sep 2010 08:14:50 -0700 Message-ID: References: <1285240926.5036.7.camel@bigi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, Linux Containers , netdev@vger.kernel.org, netfilter-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Daniel Lezcano , Linus Torvalds , Michael Kerrisk , Ulrich Drepper , Al Viro , David Miller , "Serge E. Hallyn" , Pavel Emelyanov , Pavel Emelyanov , Ben Greear , Matt Helsley , Jonathan Corbet , Sukadev Bhattiprolu , Jan Engelhardt , Patrick McHardy To: hadi@cyberus.ca Return-path: In-Reply-To: <1285240926.5036.7.camel@bigi> (jamal's message of "Thu, 23 Sep 2010 07:22:06 -0400") Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org jamal writes: > On Thu, 2010-09-23 at 01:51 -0700, Eric W. Biederman wrote: >> Take advantage of the new abstraction and allow network devices >> to be placed in any network namespace that we have a fd to talk >> about. >> > > So ... why just netdevice? could you allow migration of other > net "items" eg a route table since they are all tagged by > netns? For this patchset because we only support migrating physical network devices between network namespaces today. In the bigger picture migrating things between network namespaces is race prone. Fixing those races probably would reduce network stack performance and increase code complexity for not particularly good reason. Network devices are special because they are physical hardware and in combination with the rule that all packets coming a network device go to a single network namespace we have to implement migration for network devices. Eric