From: Chuck Lever <chuck.lever@oracle.com>
To: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v2 00/13] NFS/RDMA client-side patches proposed for 4.12
Date: Mon, 27 Mar 2017 10:05:35 -0400 [thread overview]
Message-ID: <20170327134847.20813.52412.stgit@manet.1015granger.net> (raw)
The two main improvements in this series are:
1. Break RPC-over-RDMA connections after an RPC timeout.
This gives the client's CM an opportunity to perform server and
network path rediscovery before retrying the timed-out RPC.
This design was selected because it is simple, and does not make any
changes to the normal RPC Call send hot path. Also, note the logic
already in xprt_rdma_send_request() that breaks the connection
anyway, just before sending a retransmit.
Internal testing at Oracle has demonstrated this logic is effective.
2. Support unloading the driver of the underlying device.
Full support for the DEVICE_REMOVAL CM upcall is implemented in the
client-side RPC-over-RDMA consumer. Devesh's workaround is reverted,
since it is now no longer necessary.
In addition, support is added for restoring transport operation when
a new driver is subsequently loaded or when another device is
already available with connectivity to the NFS server.
Hopefully this work can be the basis for device hotplug,
suspend/resume with NFS/RDMA mounts, and handling device failover.
Available in the "nfs-rdma-for-4.12" topic branch of this git repo:
git://git.linux-nfs.org/projects/cel/cel-2.6.git
Or for browsing:
http://git.linux-nfs.org/?p=cel/cel-2.6.git;a=log;h=refs/heads/nfs-rdma-for-4.12
Changes since v1:
- Rebased on v4.11-rc4 + recent non-rdma fixes
- Reordered so bug fixes come first
- Three small new clean ups
---
Chuck Lever (13):
xprtrdma: Cancel refresh worker during buffer shutdown
sunrpc: Export xprt_force_disconnect()
xprtrdma: Detect unreachable NFS/RDMA servers more reliably
xprtrdma: Refactor rpcrdma_ia_open()
xprtrdma: Use same device when mapping or syncing DMA buffers
xprtrdma: Support unplugging an HCA from under an NFS mount
xprtrdma: Refactor rpcrdma_ep_connect
xprtrdma: Restore transport after device removal
xprtrdma: Revert commit d0f36c46deea
xprtrdma: Annotate receive workqueue
xprtrdma: Squelch ENOBUFS warnings
sunrpc: Fix xdr_init_decode_pages() documenting comment
xprtrdma: Remove rpcrdma_buffer::rb_pool
net/sunrpc/xdr.c | 2
net/sunrpc/xprt.c | 1
net/sunrpc/xprtrdma/rpc_rdma.c | 12 +
net/sunrpc/xprtrdma/transport.c | 57 ++++++-
net/sunrpc/xprtrdma/verbs.c | 323 ++++++++++++++++++++++++++-------------
net/sunrpc/xprtrdma/xprt_rdma.h | 22 ++-
6 files changed, 295 insertions(+), 122 deletions(-)
--
Chuck Lever
next reply other threads:[~2017-03-27 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 14:05 Chuck Lever [this message]
2017-03-27 14:05 ` [PATCH v2 01/13] xprtrdma: Cancel refresh worker during buffer shutdown Chuck Lever
2017-03-27 14:05 ` [PATCH v2 02/13] sunrpc: Export xprt_force_disconnect() Chuck Lever
2017-03-27 14:05 ` [PATCH v2 03/13] xprtrdma: Detect unreachable NFS/RDMA servers more reliably Chuck Lever
2017-03-27 14:06 ` [PATCH v2 04/13] xprtrdma: Refactor rpcrdma_ia_open() Chuck Lever
2017-03-27 14:06 ` [PATCH v2 05/13] xprtrdma: Use same device when mapping or syncing DMA buffers Chuck Lever
2017-03-27 14:06 ` [PATCH v2 06/13] xprtrdma: Support unplugging an HCA from under an NFS mount Chuck Lever
2017-03-27 14:06 ` [PATCH v2 07/13] xprtrdma: Refactor rpcrdma_ep_connect Chuck Lever
2017-03-27 14:06 ` [PATCH v2 08/13] xprtrdma: Restore transport after device removal Chuck Lever
2017-03-27 14:06 ` [PATCH v2 09/13] xprtrdma: Revert commit d0f36c46deea Chuck Lever
2017-03-27 14:06 ` [PATCH v2 10/13] xprtrdma: Annotate receive workqueue Chuck Lever
2017-03-27 14:07 ` [PATCH v2 11/13] xprtrdma: Squelch ENOBUFS warnings Chuck Lever
2017-03-27 14:07 ` [PATCH v2 12/13] sunrpc: Fix xdr_init_decode_pages() documenting comment Chuck Lever
2017-03-27 14:07 ` [PATCH v2 13/13] xprtrdma: Remove rpcrdma_buffer::rb_pool 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=20170327134847.20813.52412.stgit@manet.1015granger.net \
--to=chuck.lever@oracle.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;
as well as URLs for NNTP newsgroup(s).