From: Chuck Lever <chuck.lever@oracle.com>
To: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v1 0/6] Sometimes pull up the Send buffer
Date: Thu, 17 Oct 2019 14:31:01 -0400 [thread overview]
Message-ID: <20191017182811.2517.25676.stgit@oracle-102.nfsv4bat.org> (raw)
This series contains several clean-up/refactoring patches, then the
last two patches in the series re-implement buffer pull-up for Send
buffers. After this series is applied, the client may choose between
using DMA-mapped Send buffers and pull-up. Sometimes one of these
methods is strictly more efficient than the other.
---
Chuck Lever (6):
xprtrdma: Ensure ri_id is stable during MR recycling
xprtrdma: Remove rpcrdma_sendctx::sc_xprt
xprtrdma: Remove rpcrdma_sendctx::sc_device
xprtrdma: Move the rpcrdma_sendctx::sc_wr field
xprtrdma: Refactor rpcrdma_prepare_msg_sges()
xprtrdma: Pull up sometimes
net/sunrpc/xprtrdma/backchannel.c | 2
net/sunrpc/xprtrdma/frwr_ops.c | 25 +--
net/sunrpc/xprtrdma/rpc_rdma.c | 352 ++++++++++++++++++++++++-------------
net/sunrpc/xprtrdma/verbs.c | 26 +--
net/sunrpc/xprtrdma/xprt_rdma.h | 14 -
5 files changed, 251 insertions(+), 168 deletions(-)
--
Chuck Lever
next reply other threads:[~2019-10-17 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 18:31 Chuck Lever [this message]
2019-10-17 18:31 ` [PATCH v1 1/6] xprtrdma: Ensure ri_id is stable during MR recycling Chuck Lever
2019-10-17 18:31 ` [PATCH v1 2/6] xprtrdma: Remove rpcrdma_sendctx::sc_xprt Chuck Lever
2019-10-17 18:31 ` [PATCH v1 3/6] xprtrdma: Remove rpcrdma_sendctx::sc_device Chuck Lever
2019-10-17 18:31 ` [PATCH v1 4/6] xprtrdma: Move the rpcrdma_sendctx::sc_wr field Chuck Lever
2019-10-17 18:31 ` [PATCH v1 5/6] xprtrdma: Refactor rpcrdma_prepare_msg_sges() Chuck Lever
2019-10-17 18:31 ` [PATCH v1 6/6] xprtrdma: Pull up sometimes Chuck Lever
2019-10-18 20:17 ` Tom Talpey
2019-10-18 23:34 ` Chuck Lever
2019-10-19 16:36 ` Tom Talpey
2019-10-22 16:08 ` Chuck Lever
2019-10-26 2:04 ` Tom Talpey
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=20191017182811.2517.25676.stgit@oracle-102.nfsv4bat.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.