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 v3 0/7] SUNRPC: initial part of making pipefs work in net ns
Date: Mon, 26 Dec 2011 15:38:48 +0300 [thread overview]
Message-ID: <20111226113504.13216.19798.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.
v3:
1) Rebased on tag "v3.2-rc7".
v2:
1) Rebased of current repo state (i.e. all commits were pulled before apply)
This patch-set implements pipefs superblock creation per network namespace
context instead of using single one for all possible contexts. Also, it
provides pipefs dentries creation and destruction helpers for kernel routines.
Additional description of the idea about how to make RPC pipefs work per
network namespace context can be found in the letter titled "SUNRPC: "RPC
pipefs per network namespace" preparations", which has been sent already to
linux-nfs@vger.kernel.org.
The following series consists of:
---
Stanislav Kinsbursky (7):
SUNRPC: create RPC pipefs superblock per network namespace context
SUNRPC: hold current network namespace while pipefs superblock is active
SUNRPC: send notification events on pipefs sb creation and destruction
SUNRPC: pipefs dentry lookup helper introduced
SUNRPC: put pipefs superblock link on network namespace
SUNRPC: pipefs per-net operations helper introduced
SUNRPC: added debug messages to RPC pipefs
include/linux/sunrpc/rpc_pipe_fs.h | 14 ++++
net/sunrpc/netns.h | 3 +
net/sunrpc/rpc_pipe.c | 113 +++++++++++++++++++++++++++++++++++-
net/sunrpc/sunrpc_syms.c | 1
4 files changed, 129 insertions(+), 2 deletions(-)
--
Signature
next reply other threads:[~2011-12-26 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 12:38 Stanislav Kinsbursky [this message]
2011-12-26 12:38 ` [PATCH v3 1/7] SUNRPC: create RPC pipefs superblock per network namespace context Stanislav Kinsbursky
2011-12-26 12:39 ` [PATCH v3 2/7] SUNRPC: hold current network namespace while pipefs superblock is active Stanislav Kinsbursky
2011-12-26 12:39 ` [PATCH v3 3/7] SUNRPC: send notification events on pipefs sb creation and destruction Stanislav Kinsbursky
2011-12-26 12:39 ` [PATCH v3 4/7] SUNRPC: pipefs dentry lookup helper introduced Stanislav Kinsbursky
2011-12-26 12:39 ` [PATCH v3 5/7] SUNRPC: put pipefs superblock link on network namespace Stanislav Kinsbursky
2011-12-26 12:39 ` [PATCH v3 6/7] SUNRPC: pipefs per-net operations helper introduced Stanislav Kinsbursky
2011-12-26 12:39 ` [PATCH v3 7/7] SUNRPC: added debug messages to RPC pipefs 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=20111226113504.13216.19798.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).