From: Chuck Lever <chuck.lever@oracle.com>
To: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v1 00/19] Proposed NFS/RDMA patches for v5.2
Date: Wed, 10 Apr 2019 16:06:31 -0400 [thread overview]
Message-ID: <20190410200446.11522.21145.stgit@manet.1015granger.net> (raw)
For review, this is a series of minor clean-ups, bug fixes, and
performance optimizations.
See also:
http://git.linux-nfs.org/?p=cel/cel-2.6.git;a=shortlog;h=refs/heads/nfs-for-5.2
---
Chuck Lever (19):
SUNRPC: Avoid digging into the ATOMIC pool
xprtrdma: Fix an frwr_map recovery nit
xprtrdma: Defer completion only when local invalidation is needed
xprtrdma: Clean up rpcrdma_create_req()
xprtrdma: Clean up rpcrdma_create_rep() and rpcrdma_destroy_rep()
xprtrdma: rpcrdma_regbuf alignment
xprtrdma: Allocate req's regbufs at xprt create time
xprtrdma: De-duplicate "allocate new, free old regbuf"
xprtrdma: Clean up regbuf helpers
xprtrdma: Backchannel can use GFP_KERNEL allocations
xprtrdma: Increase maximum number of backchannel request
xprtrdma: Trace marshaling failures
xprtrdma: Clean up sendctx functions
xprtrdma: More Send completion batching
xprtrdma: Eliminate rpcrdma_ia::ri_device
SUNRPC: Update comments based on recent changes
xprtrdma: Remove rpcrdma_create_data_internal::rsize and wsize
xprtrdma: Aggregate the inline settings in struct rpcrdma_ep
xprtrdma: Eliminate struct rpcrdma_create_data_internal
include/trace/events/rpcrdma.h | 27 +++
net/sunrpc/socklib.c | 2
net/sunrpc/xprt.c | 4
net/sunrpc/xprtrdma/backchannel.c | 120 +++++---------
net/sunrpc/xprtrdma/frwr_ops.c | 40 ++---
net/sunrpc/xprtrdma/rpc_rdma.c | 146 +++++++++--------
net/sunrpc/xprtrdma/transport.c | 103 ++----------
net/sunrpc/xprtrdma/verbs.c | 327 +++++++++++++++++++++----------------
net/sunrpc/xprtrdma/xprt_rdma.h | 114 ++++++-------
9 files changed, 430 insertions(+), 453 deletions(-)
--
Chuck Lever
next reply other threads:[~2019-04-10 20:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 20:06 Chuck Lever [this message]
2019-04-10 20:06 ` [PATCH v1 01/19] SUNRPC: Avoid digging into the ATOMIC pool Chuck Lever
2019-04-10 20:06 ` [PATCH v1 02/19] xprtrdma: Fix an frwr_map recovery nit Chuck Lever
2019-04-10 20:06 ` [PATCH v1 03/19] xprtrdma: Defer completion only when local invalidation is needed Chuck Lever
2019-04-10 20:06 ` [PATCH v1 04/19] xprtrdma: Clean up rpcrdma_create_req() Chuck Lever
2019-04-10 20:06 ` [PATCH v1 05/19] xprtrdma: Clean up rpcrdma_create_rep() and rpcrdma_destroy_rep() Chuck Lever
2019-04-11 20:47 ` Anna Schumaker
2019-04-10 20:07 ` [PATCH v1 06/19] xprtrdma: rpcrdma_regbuf alignment Chuck Lever
2019-04-10 20:07 ` [PATCH v1 07/19] xprtrdma: Allocate req's regbufs at xprt create time Chuck Lever
2019-04-10 20:07 ` [PATCH v1 08/19] xprtrdma: De-duplicate "allocate new, free old regbuf" Chuck Lever
2019-04-10 20:07 ` [PATCH v1 09/19] xprtrdma: Clean up regbuf helpers Chuck Lever
2019-04-10 20:07 ` [PATCH v1 10/19] xprtrdma: Backchannel can use GFP_KERNEL allocations Chuck Lever
2019-04-10 20:07 ` [PATCH v1 11/19] xprtrdma: Increase maximum number of backchannel request Chuck Lever
2019-04-10 20:07 ` [PATCH v1 12/19] xprtrdma: Trace marshaling failures Chuck Lever
2019-04-10 20:07 ` [PATCH v1 13/19] xprtrdma: Clean up sendctx functions Chuck Lever
2019-04-10 20:07 ` [PATCH v1 14/19] xprtrdma: More Send completion batching Chuck Lever
2019-04-10 20:07 ` [PATCH v1 15/19] xprtrdma: Eliminate rpcrdma_ia::ri_device Chuck Lever
2019-04-10 20:07 ` [PATCH v1 16/19] SUNRPC: Update comments based on recent changes Chuck Lever
2019-04-10 20:08 ` [PATCH v1 17/19] xprtrdma: Remove rpcrdma_create_data_internal::rsize and wsize Chuck Lever
2019-04-10 20:08 ` [PATCH v1 18/19] xprtrdma: Aggregate the inline settings in struct rpcrdma_ep Chuck Lever
2019-04-10 20:08 ` [PATCH v1 19/19] xprtrdma: Eliminate struct rpcrdma_create_data_internal 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=20190410200446.11522.21145.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