From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423369AbWF1OgB (ORCPT ); Wed, 28 Jun 2006 10:36:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423368AbWF1OgA (ORCPT ); Wed, 28 Jun 2006 10:36:00 -0400 Received: from mailhub.sw.ru ([195.214.233.200]:62493 "EHLO relay.sw.ru") by vger.kernel.org with ESMTP id S1423366AbWF1Of7 (ORCPT ); Wed, 28 Jun 2006 10:35:59 -0400 Message-ID: <44A29379.6060609@sw.ru> Date: Wed, 28 Jun 2006 18:34:33 +0400 From: Kirill Korotaev User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060417 X-Accept-Language: en-us, en, ru MIME-Version: 1.0 To: Andrey Savochkin CC: Daniel Lezcano , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, serue@us.ibm.com, haveblue@us.ibm.com, clg@fr.ibm.com, Andrew Morton , herbert@13thfloor.at, devel@openvz.org, sam@vilain.net, ebiederm@xmission.com, viro@ftp.linux.org.uk, alexey@sw.ru, Cedric Le Goater Subject: Re: [patch 3/4] Network namespaces: IPv4 FIB/routing in namespaces References: <20060626134945.A28942@castle.nmd.msu.ru> <20060626135250.B28942@castle.nmd.msu.ru> <20060626135427.C28942@castle.nmd.msu.ru> <449FF5AE.2040201@fr.ibm.com> <44A28964.2090006@fr.ibm.com> <20060628183015.B31885@castle.nmd.msu.ru> In-Reply-To: <20060628183015.B31885@castle.nmd.msu.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >>>>Structures related to IPv4 rounting (FIB and routing cache) >>>>are made per-namespace. >> >>Hi Andrey, >> >>if the ressources are private to the namespace, how do you will handle >>NFS mounted before creating the network namespace ? Do you take care of >>that or simply assume you can't access NFS anymore ? > > > This is a question that brings up another level of interaction between > networking and the rest of kernel code. > Solution that I use now makes the NFS communication part always run in > the root namespace. This is discussable, of course, but it's a far more > complicated matter than just device lists or routing :) if we had containers (not namespaces) then it would be also possible to run NFS in context of the appropriate container and thus each user could mount NFS itself with correct networking context. it's another thing which ties subsytems and makes namespaces ugly :/ Kirill