From: <andros@netapp.com>
To: <trond.myklebust@primarydata.com>
Cc: <steved@redhat.com>, <linux-nfs@vger.kernel.org>,
Andy Adamson <andros@netapp.com>
Subject: [PATCH Version 3 0/9] NFSV4.1,2 session trunking
Date: Wed, 27 Apr 2016 11:36:01 -0400 [thread overview]
Message-ID: <1461771370-16375-1-git-send-email-andros@netapp.com> (raw)
From: Andy Adamson <andros@netapp.com>
RFC patchset.
Please review the code.
Main question: Do we want to use multiple hostnames on the mount command to
communicate the NFSv4.1 session trunking addresses, or only use (yet
to be coded) fs_locations_info?
This patch set uses multiple hostnames on the mount commnad and so requires
nfs-utils changes to mount.nfs from the Version 3 "Add multihostname support
for NFSv4.1,2" nfs-utils patchset.
Notes:
I did not call EXCHANGE_ID on the mulihostnames in the state
manager, as they are synchronous RPC calls that occur directly after
the nfs_client->cl_rpcclient has been established. I can change this
if needed.
I do not have code to call BIND_CONN_TO_SESSION if sp4_how is not SP4_NONE.
I added a "multiaddr=" option to the mtab for each multiaddr successfully
added to the xprt_switch.
If we want to keep the multiple hostnames on the mount command method of
expressing NFSv4.1 session trunking addresses, we should fix this:
- v3 mounts with multiple hostnames succeeds but adds an mtab dev entry that
omits the ":/<exported dir> and so prints a warning at umount.
Please review. I will start the fs_locations_info method of expressing the
session trunking addresses.
Thanks
--> Andy
NFS parse multiple hostnames
NFS default callback ops
NFS refactor nfs4_match_clientids
NFS refactor nfs4_check_serverowner_major_id
NFS detect session trunking
NFS refactor _nfs4_proc_exchange_id for session trunking
SUNRPC add flag to rpc_task_release_client
NFS test and add multi-addrs for session trunking
NFS add multiaddr to nfs_show_nfsv4_options
fs/nfs/internal.h | 19 ++++++
fs/nfs/nfs4_fs.h | 9 +++
fs/nfs/nfs4client.c | 141 ++++++++++++++++++++++++++++++++++++++++----
fs/nfs/nfs4proc.c | 79 +++++++++++++++++++++----
fs/nfs/super.c | 64 ++++++++++++++++++++
include/linux/sunrpc/clnt.h | 2 +-
net/sunrpc/clnt.c | 6 +-
net/sunrpc/sched.c | 2 +-
net/sunrpc/xprtmultipath.c | 4 ++
9 files changed, 300 insertions(+), 26 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-04-27 15:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 15:36 andros [this message]
2016-04-27 15:36 ` [PATCH Version 3 1/9] NFS parse multiple hostnames andros
2016-04-27 15:36 ` [PATCH Version 3 2/9] NFS default callback ops andros
2016-04-27 15:36 ` [PATCH Version 3 3/9] NFS refactor nfs4_match_clientids andros
2016-04-27 15:36 ` [PATCH Version 3 4/9] NFS refactor nfs4_check_serverowner_major_id andros
2016-04-27 15:36 ` [PATCH Version 3 5/9] NFS detect session trunking andros
2016-04-27 15:36 ` [PATCH Version 3 6/9] NFS refactor _nfs4_proc_exchange_id for " andros
2016-04-27 15:36 ` [PATCH Version 3 7/9] SUNRPC add flag to rpc_task_release_client andros
2016-04-27 15:36 ` [PATCH Version 3 8/9] NFS test and add multi-addrs for session trunking andros
2016-04-27 15:36 ` [PATCH Version 3 9/9] NFS add multiaddr to nfs_show_nfsv4_options andros
2016-04-27 18:05 ` Weston Andros Adamson
2016-04-27 18:32 ` Adamson, Andy
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=1461771370-16375-1-git-send-email-andros@netapp.com \
--to=andros@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
--cc=trond.myklebust@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).