From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from mailhub.sw.ru ([195.214.232.25]:18200 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754998Ab1J1JlG (ORCPT ); Fri, 28 Oct 2011 05:41:06 -0400 Message-ID: <4EAA78DD.2000408@parallels.com> Date: Fri, 28 Oct 2011 13:41:49 +0400 From: Stanislav Kinsbursky MIME-Version: 1.0 To: "J. Bruce Fields" CC: "Trond.Myklebust@netapp.com" , "linux-nfs@vger.kernel.org" , Pavel Emelianov , "neilb@suse.de" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "davem@davemloft.net" , "devel@openvz.org" Subject: Re: [PATCH v3 0/3] SUNRPC: rcbind clients virtualization References: <20111027180824.20459.23219.stgit@localhost6.localdomain6> <20111027202514.GA31669@fieldses.org> <4EAA74DD.3070708@parallels.com> <20111028093036.GA2604@fieldses.org> In-Reply-To: <20111028093036.GA2604@fieldses.org> Content-Type: text/plain; charset=UTF-8; format=flowed Sender: linux-nfs-owner@vger.kernel.org List-ID: 28.10.2011 13:30, J. Bruce Fields пишет: > On Fri, Oct 28, 2011 at 01:24:45PM +0400, Stanislav Kinsbursky wrote: >> This patch-set was created before you've sent your NFSd plan and we >> disacussed Lockd per netns. >> So, this sentence: "NFSd service will be per netns too from my pow" >> is obsolete. And Lockd will be one for all. > > I believe lockd should be pert-netns--at least that's what the server > needs. > > (The single lockd thread may handle requests from all netns, but it > should behave like a different service depending on netns, so its data > structures, etc. will need to be per-ns. > Sure. Looks like we have misunderstanding here. When I said, that Lockd should be one for all, I meaned, that we will have only one kthread for all ns (not one per ns). Private data will be per net ns, of course. BTW, Bruce, please, have a brief look at my e-mail to linux-nfs@vger.kernel.org named "SUNRPC: non-exclusive pipe creation". I've done a lot in "RPC pipefs per net ns" task, and going to send first patches soon. But right now I'm really confused will this non-exclusive pipes creation and almost ready so remove this functionality. But I'm afraid, that I've missed something. Would be greatly appreciate for your opinion about my question. > --b. > >> Or you are asking about something else? >> >>> --b. >>> >>>> And also we have NFSd file system, which >>>> is not virtualized yet. >>>> >>>> The following series consists of: >>>> >>>> --- >>>> >>>> Stanislav Kinsbursky (3): >>>> SUNRPC: move rpcbind internals to sunrpc part of network namespace context >>>> SUNRPC: optimize net_ns dereferencing in rpcbind creation calls >>>> SUNRPC: optimize net_ns dereferencing in rpcbind registering calls >>>> >>>> >>>> net/sunrpc/netns.h | 5 ++ >>>> net/sunrpc/rpcb_clnt.c | 103 ++++++++++++++++++++++++++---------------------- >>>> 2 files changed, 61 insertions(+), 47 deletions(-) >>>> >>>> -- >>>> Signature >> >> >> -- >> Best regards, >> Stanislav Kinsbursky -- Best regards, Stanislav Kinsbursky