From: Jim Rees <rees@umich.edu>
To: bhalevy@panasas.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] complex block layout
Date: Wed, 21 Jul 2010 18:29:38 -0400 [thread overview]
Message-ID: <cover.1279743856.git.rees@umich.edu> (raw)
This is a replacement for the patch set I sent last week, rebased to current
pnfs-all-latest and incorporating suggestions both from reviewers and from
checkpatch.pl.
These two patches move the complex block layout device mapping from the
kernel to a user space daemon. The first patch adds a simple upcall
mechanism via pipefs for the kernel piece to communicate with the daemon.
The second patch removes the kernel device mapping and replaces it with
calls to the daemon.
Passes Connectathon tests to both EMC and spnfs servers.
The user daemon will be sent separately as a patch to nfs-utils.
Haiying Tang (2):
pnfs-block: Add support for simple rpc pipefs
pnfs-block: Remove device creation from kernel
fs/nfs/blocklayout/Makefile | 2 +-
fs/nfs/blocklayout/block-device-discovery-pipe.c | 66 +++
fs/nfs/blocklayout/blocklayout.c | 15 +-
fs/nfs/blocklayout/blocklayout.h | 18 +-
fs/nfs/blocklayout/blocklayoutdev.c | 494 +++-------------------
fs/nfs/blocklayout/blocklayoutdm.c | 297 ++-----------
include/linux/sunrpc/rpc_pipe_fs.h | 4 +
include/linux/sunrpc/simple_rpc_pipefs.h | 111 +++++
net/sunrpc/Makefile | 2 +-
net/sunrpc/simple_rpc_pipefs.c | 424 +++++++++++++++++++
10 files changed, 721 insertions(+), 712 deletions(-)
create mode 100644 fs/nfs/blocklayout/block-device-discovery-pipe.c
create mode 100644 include/linux/sunrpc/simple_rpc_pipefs.h
create mode 100644 net/sunrpc/simple_rpc_pipefs.c
next reply other threads:[~2010-07-21 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 22:29 Jim Rees [this message]
2010-07-21 22:30 ` [PATCH 1/2] pnfs-block: Add support for simple rpc pipefs Jim Rees
2010-07-21 22:30 ` [PATCH 2/2] pnfs-block: Remove device creation from kernel Jim Rees
2010-07-26 6:58 ` [PATCH 0/2] complex block layout Benny Halevy
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=cover.1279743856.git.rees@umich.edu \
--to=rees@umich.edu \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
/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).