From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Lamparter Subject: Re: [PATCH 7/8] net: Allow setting the network namespace by fd Date: Thu, 23 Sep 2010 16:58:56 +0200 Message-ID: <20100923145856.GB1160234@jupiter.n2.diac24.net> References: <1285240926.5036.7.camel@bigi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1285240926.5036.7.camel@bigi> Sender: netdev-owner@vger.kernel.org To: jamal Cc: "Eric W. Biederman" , 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 List-Id: containers.vger.kernel.org On Thu, Sep 23, 2010 at 07:22:06AM -0400, jamal wrote: > 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? migrating route table entries makes no sense because a) they refer to devices and configuration that does not exist in the target namespace; they only make sense within their netns context b) they are purely virtual and you get the same result from deleting and recreating them. Network devices are special because they may have something attached to them, be it hardware or some daemon. -David