From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: Trond.Myklebust@netapp.com, linux-nfs@vger.kernel.org,
xemul@parallels.com, 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
Date: Thu, 27 Oct 2011 16:25:14 -0400 [thread overview]
Message-ID: <20111027202514.GA31669@fieldses.org> (raw)
In-Reply-To: <20111027180824.20459.23219.stgit@localhost6.localdomain6>
On Thu, Oct 27, 2011 at 10:10:43PM +0300, Stanislav Kinsbursky wrote:
> v3:
> 1) First two patches from previous version were squashed.
>
> This patch-set was created in context of clone of git branch:
> git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git
> and rebased on tag "v3.1".
>
> This patch-set virtualizes rpcbind clients per network namespace context. IOW,
> each network namespace will have its own pair of rpcbind clients (if they would
> be created by request).
>
> Note:
> 1) this patch-set depends on "SUNRPC: make rpcbind clients allocated and
> destroyed dynamically" patch-set which has been send earlier.
> 2) init_net pointer is still used instead of current->nsproxy->net_ns,
> because I'm not sure yet about how to virtualize services. I.e. NFS callback
> services will be per netns. NFSd service will be per netns too from my pow. But
> Lockd can be per netns or one for all.
I'm not sure what you mean by that; could you explain?
--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
next prev parent reply other threads:[~2011-10-27 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 19:10 [PATCH v3 0/3] SUNRPC: rcbind clients virtualization Stanislav Kinsbursky
2011-10-27 19:11 ` [PATCH v3 1/3] SUNRPC: move rpcbind internals to sunrpc part of network namespace context Stanislav Kinsbursky
2011-10-27 19:11 ` [PATCH v3 2/3] SUNRPC: optimize net_ns dereferencing in rpcbind creation calls Stanislav Kinsbursky
2011-10-27 19:30 ` [PATCH v3 3/3] SUNRPC: optimize net_ns dereferencing in rpcbind registering calls Stanislav Kinsbursky
2011-10-27 20:25 ` J. Bruce Fields [this message]
2011-10-28 9:24 ` [PATCH v3 0/3] SUNRPC: rcbind clients virtualization Stanislav Kinsbursky
2011-10-28 9:30 ` J. Bruce Fields
2011-10-28 9:41 ` Stanislav Kinsbursky
2011-11-04 22:10 ` J. Bruce Fields
2011-11-07 8:02 ` Stanislav Kinsbursky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111027202514.GA31669@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=skinsbursky@parallels.com \
--cc=xemul@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).