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/2] Add multihostname support for NFSv4.1,2
Date: Wed, 27 Apr 2016 11:36:45 -0400 [thread overview]
Message-ID: <1461771407-16423-1-git-send-email-andros@netapp.com> (raw)
From: Andy Adamson <andros@netapp.com>
RFC patchset
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?
The multiple hostnames on the mount command are added to a new multiaddr
option and passed to the kernel for consumption.
This code requires the kernel "Version 3 NFSV4.1,2 session trunking"
patch set.
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.
- need to update the manpage
-->Andy
Andy Adamson (2):
NFS parse NFSv4 multiple hostnames
NFS add multiaddr mount option
utils/mount/parse_dev.c | 30 +++++++++++++++--------
utils/mount/parse_dev.h | 2 +-
utils/mount/stropts.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++++-
utils/mount/utils.c | 2 +-
4 files changed, 84 insertions(+), 13 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-04-27 15:37 UTC|newest]
Thread overview: 13+ 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/2] NFS parse NFSv4 multiple hostnames andros
2016-04-27 15:36 ` [PATCH Version 3 2/2] NFS add multiaddr mount option andros
2016-04-29 14:12 ` [PATCH Version 3 0/2] Add multihostname support for NFSv4.1,2 Steve Dickson
2016-04-29 14:27 ` Adamson, Andy
2016-04-29 14:46 ` Steve Dickson
2016-04-29 15:09 ` Adamson, Andy
2016-04-29 15:24 ` Chuck Lever
2016-04-29 15:50 ` Steve Dickson
2016-04-29 15:53 ` Anna Schumaker
2016-04-29 18:05 ` J. Bruce Fields
2016-04-29 19:39 ` Anna Schumaker
2016-04-29 20:03 ` J. Bruce Fields
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=1461771407-16423-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).