From: <andros@netapp.com>
To: <steved@redhat.com>
Cc: <linux-nfs@vger.kernel.org>, Andy Adamson <andros@netapp.com>
Subject: [PATCH 0/2] Add multihostname support for NFSv4.1,2
Date: Wed, 24 Feb 2016 12:55:57 -0500 [thread overview]
Message-ID: <1456336559-17334-1-git-send-email-andros@netapp.com> (raw)
From: Andy Adamson <andros@netapp.com>
This code requires the kernel "Version 2 NFSV4.1,2 session trunking"
patch set.
Note that while being useful for testing, it is not yet decided if
expressing session trunking hosts in this manner is the best way forward.
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 | 62 ++++++++++++++++++++++++++++++++++++++++++++++++-
utils/mount/utils.c | 2 +-
4 files changed, 83 insertions(+), 13 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-02-24 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 17:55 andros [this message]
2016-02-24 17:55 ` [PATCH 1/2] NFS parse NFSv4 multiple hostnames andros
2016-03-16 15:26 ` Steve Dickson
2016-04-20 14:39 ` Adamson, Andy
2016-02-24 17:55 ` [PATCH 2/2] NFS add multiaddr mount option andros
2016-03-16 15:24 ` Steve Dickson
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=1456336559-17334-1-git-send-email-andros@netapp.com \
--to=andros@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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).