From: Jeff Layton <jlayton@poochiereds.net>
To: bfields@fieldses.org, anna.schumaker@netapp.com, trondmy@primarydata.com
Cc: tigran.mkrtchyan@desy.de, thomas.haynes@primarydata.com,
linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] pnfs/nfsd: have client and server support multiple layout types
Date: Tue, 7 Jun 2016 06:38:08 -0400 [thread overview]
Message-ID: <1465295891-4952-1-git-send-email-jlayton@poochiereds.net> (raw)
This is a follow-up to the RFC set that I sent a week ago.
The basic idea is to allow the client to handle lists of layout types,
and for the server to provide them when there are multiple layout types
available for a particular filesystem.
The main change since the RFC set is to change how the client-side
layout driver selection code works. I dropped the patch that I had
written for the client and picked up Tigran's instead, and added a
patch on top to change the selection order.
Only lightly tested by mounting a server that sends both flexfiles and
block layouts. The client successfully selected the block layout in most
cases, but if I blacklist blocklayoutdriver then it selects flexfiles
instead.
I'm sending these together, but I'd expect Bruce to pick up the nfsd
patches and Trond or Anna to pick up the client-side ones.
The nfsd patch is based on top of Tom's nfsd flexfile layout patches.
Probably we should squash patches 2 and 3 before merging, but I left
them apart for now so you can see the change on top of what Tigran
originally proposed.
Jeff Layton (2):
nfsd: allow nfsd to advertise multiple layout types
pnfs: add a new mechanism to select a layout driver according to an
ordered list
Tigran Mkrtchyan (1):
pnfs support servers with multiple layout types
fs/nfs/client.c | 2 +-
fs/nfs/nfs4xdr.c | 23 +++++++--------
fs/nfs/pnfs.c | 76 ++++++++++++++++++++++++++++++++++++++++---------
fs/nfs/pnfs.h | 2 +-
fs/nfsd/export.c | 4 +--
fs/nfsd/export.h | 2 +-
fs/nfsd/nfs4layouts.c | 6 ++--
fs/nfsd/nfs4proc.c | 4 +--
fs/nfsd/nfs4xdr.c | 30 +++++++++----------
include/linux/nfs_xdr.h | 8 +++++-
10 files changed, 103 insertions(+), 54 deletions(-)
--
2.5.5
next reply other threads:[~2016-06-07 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 10:38 Jeff Layton [this message]
2016-06-07 10:38 ` [PATCH 1/3] nfsd: allow nfsd to advertise multiple layout types Jeff Layton
2016-06-07 10:38 ` [PATCH 2/3] pnfs support servers with " Jeff Layton
2016-06-07 21:33 ` J. Bruce Fields
2016-06-08 10:34 ` Jeff Layton
2016-06-07 10:38 ` [PATCH 3/3] pnfs: add a new mechanism to select a layout driver according to an ordered list Jeff Layton
2016-06-07 21:46 ` J. Bruce Fields
2016-06-08 10:36 ` Jeff Layton
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=1465295891-4952-1-git-send-email-jlayton@poochiereds.net \
--to=jlayton@poochiereds.net \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=thomas.haynes@primarydata.com \
--cc=tigran.mkrtchyan@desy.de \
--cc=trondmy@primarydata.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).