netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org, xemul@parallels.com, neilb@suse.de,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	jbottomley@parallels.com, bfields@fieldses.org,
	davem@davemloft.net, devel@openvz.org
Subject: [PATCH v5 0/6] SUNRPC: rcbind clients virtualization
Date: Fri, 13 Jan 2012 12:52:01 +0400	[thread overview]
Message-ID: <20120113084545.31750.83655.stgit@localhost6.localdomain6> (raw)

This patch-set was created in context of clone of git branch:
git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git.
head: devel

v5:
1) Rebased on up-to-date state ("devel" head).
2) Added two more patches from latter series ("SUNRPC: register services with
per-net rpcbind"), because logically this series is the more suitable place for
them.

v4:
1) Rebased of current repo state (i.e. all commits pulled before apply)

v3:
1) First two patches from previous version were squashed.

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).

The following series consists of:

---

Stanislav Kinsbursky (6):
      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
      SUNRPC: create rpcbind client in passed network namespace context
      SUNRPC: register rpcbind programs in passed network namespase context
      SUNRPC: parametrize local rpcbind clients creation with net ns


 include/linux/sunrpc/clnt.h |    9 ++-
 net/sunrpc/netns.h          |    5 ++
 net/sunrpc/rpcb_clnt.c      |  121 +++++++++++++++++++++++--------------------
 net/sunrpc/svc.c            |   14 ++---
 4 files changed, 82 insertions(+), 67 deletions(-)

             reply	other threads:[~2012-01-13  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13  8:52 Stanislav Kinsbursky [this message]
2012-01-13  8:52 ` [PATCH v5 1/6] SUNRPC: move rpcbind internals to sunrpc part of network namespace context Stanislav Kinsbursky
2012-01-13  8:52 ` [PATCH v5 2/6] SUNRPC: optimize net_ns dereferencing in rpcbind creation calls Stanislav Kinsbursky
2012-01-13  8:52 ` [PATCH v5 3/6] SUNRPC: optimize net_ns dereferencing in rpcbind registering calls Stanislav Kinsbursky
2012-01-13  8:52 ` [PATCH v5 4/6] SUNRPC: create rpcbind client in passed network namespace context Stanislav Kinsbursky
2012-01-13  8:52 ` [PATCH v5 5/6] SUNRPC: register rpcbind programs in passed network namespase context Stanislav Kinsbursky
2012-01-13  8:52 ` [PATCH v5 6/6] SUNRPC: parametrize local rpcbind clients creation with net ns Stanislav Kinsbursky
2012-01-13 10:03 ` [PATCH v5 0/6] SUNRPC: rcbind clients virtualization 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=20120113084545.31750.83655.stgit@localhost6.localdomain6 \
    --to=skinsbursky@parallels.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=davem@davemloft.net \
    --cc=devel@openvz.org \
    --cc=jbottomley@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=netdev@vger.kernel.org \
    --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).