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 v2 0/4] Last NFS/RDMA client patches for v4.15
Date: Mon, 30 Oct 2017 16:21:40 -0400 [thread overview]
Message-ID: <20171030201903.8146.45897.stgit@manet.1015granger.net> (raw)
Here's my final set of NFS/RDMA client patches for v4.15.
Three of these are clean up patches. The first patch is an important
change, however.
In the earlier set of patches, I changed the Receive CQ to run in
workqueue context. Here, I change the Send CQ to also run in
workqueue context.
In addition, I move it to a different compvec than the Receive CQ.
My performance measurements show that the two completion handlers
interfere with each other if they run in the same workqueue thread.
Please consider this set for v4.15.
Changes since the initial posting:
- Added Reviewed-by: tags to three of these
- Addressed Devesh's patch description comment
---
Chuck Lever (4):
xprtrdma: Put Send CQ in IB_POLL_WORKQUEUE mode
rpcrdma: Remove C structure definitions of XDR data items
xprtrdma: Remove include for linux/prefetch.h
xprtrdma: Update copyright notices
include/linux/sunrpc/rpc_rdma.h | 60 +--------------------------------------
net/sunrpc/xprtrdma/rpc_rdma.c | 7 +++--
net/sunrpc/xprtrdma/transport.c | 1 +
net/sunrpc/xprtrdma/verbs.c | 4 +--
net/sunrpc/xprtrdma/xprt_rdma.h | 7 +----
5 files changed, 9 insertions(+), 70 deletions(-)
--
Chuck Lever
next reply other threads:[~2017-10-30 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 20:21 Chuck Lever [this message]
2017-10-30 20:21 ` [PATCH v2 1/4] xprtrdma: Put Send CQ in IB_POLL_WORKQUEUE mode Chuck Lever
2017-10-30 20:21 ` [PATCH v2 2/4] rpcrdma: Remove C structure definitions of XDR data items Chuck Lever
2017-10-30 20:22 ` [PATCH v2 3/4] xprtrdma: Remove include for linux/prefetch.h Chuck Lever
2017-10-30 20:22 ` [PATCH v2 4/4] xprtrdma: Update copyright notices 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=20171030201903.8146.45897.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;
as well as URLs for NNTP newsgroup(s).