From: Chuck Lever <chuck.lever@oracle.com>
To: anna.schumaker@netapp.com
Cc: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v1 0/4] Use same proto= after traversing a referral
Date: Mon, 04 Dec 2017 14:13:22 -0500 [thread overview]
Message-ID: <20171204190904.18629.70341.stgit@manet.1015granger.net> (raw)
Hi Anna-
Today when the Linux client traverses an NFSv4 referral, it always
chooses proto=tcp on the submount. This means following a referral
on an NFS/RDMA mount will always make the submounts use TCP, which
is not desirable. These patches make the client try NFS/RDMA first
when traversing a referral so that submounts will continue to use
NFS/RDMA.
Please consider this series for v4.16.
---
Chuck Lever (4):
nfs: Define NFS_RDMA_PORT
nfs: Referrals should use the same proto setting as their parent
nfs: Update server port after referral or migration
SUNRPC: Remove rpc_protocol()
fs/nfs/nfs4client.c | 24 +++++++++++++++++++++---
fs/nfs/nfs4namespace.c | 2 --
include/linux/sunrpc/clnt.h | 1 -
include/uapi/linux/nfs.h | 1 +
net/sunrpc/clnt.c | 16 ----------------
5 files changed, 22 insertions(+), 22 deletions(-)
--
Chuck Lever
next reply other threads:[~2017-12-04 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 19:13 Chuck Lever [this message]
2017-12-04 19:13 ` [PATCH v1 1/4] nfs: Define NFS_RDMA_PORT Chuck Lever
2017-12-05 15:09 ` Devesh Sharma
2017-12-05 18:49 ` Chuck Lever
2017-12-06 6:04 ` Devesh Sharma
2017-12-06 14:52 ` Chuck Lever
2017-12-06 16:42 ` Devesh Sharma
2017-12-04 19:13 ` [PATCH v1 2/4] nfs: Referrals should use the same proto setting as their parent Chuck Lever
2017-12-05 15:36 ` Anna Schumaker
2017-12-05 19:04 ` Chuck Lever
2017-12-13 15:15 ` Chuck Lever
2017-12-04 19:13 ` [PATCH v1 3/4] nfs: Update server port after referral or migration Chuck Lever
2017-12-04 19:13 ` [PATCH v1 4/4] SUNRPC: Remove rpc_protocol() Chuck Lever
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=20171204190904.18629.70341.stgit@manet.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@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