From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: [PATCH v1 0/6] Refactor path that sends error responses
Date: Mon, 22 Jun 2020 17:00:59 -0400 [thread overview]
Message-ID: <20200622205906.2144.43930.stgit@klimt.1015granger.net> (raw)
There are currently two paths in the server's RPC/RDMA implementation
for sending error responses. De-duplicate these two into one set of
helpers.
---
Chuck Lever (6):
svcrdma: Fix page leak in svc_rdma_recv_read_chunk()
svcrdma: Remove save_io_pages() call from send_error_msg()
svcrdma: Add @rctxt parameter to svc_rdma_send_error() functions
svcrdma: Add a @status parameter to svc_rdma_send_error_msg()
svcrdma: Eliminate return value for svc_rdma_send_error_msg()
svcrdma: Make svc_rdma_send_error_msg() a global function
include/linux/sunrpc/svc_rdma.h | 4 ++
net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 9 +--
net/sunrpc/xprtrdma/svc_rdma_sendto.c | 85 +++++++++++++++++--------
3 files changed, 68 insertions(+), 30 deletions(-)
--
Chuck Lever
next reply other threads:[~2020-06-22 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 21:00 Chuck Lever [this message]
2020-06-22 21:01 ` [PATCH v1 1/6] svcrdma: Fix page leak in svc_rdma_recv_read_chunk() Chuck Lever
2020-06-22 21:01 ` [PATCH v1 2/6] svcrdma: Remove save_io_pages() call from send_error_msg() Chuck Lever
2020-06-22 21:01 ` [PATCH v1 3/6] svcrdma: Add @rctxt parameter to svc_rdma_send_error() functions Chuck Lever
2020-06-22 21:01 ` [PATCH v1 4/6] svcrdma: Add a @status parameter to svc_rdma_send_error_msg() Chuck Lever
2020-06-22 21:01 ` [PATCH v1 5/6] svcrdma: Eliminate return value for svc_rdma_send_error_msg() Chuck Lever
2020-06-22 21:01 ` [PATCH v1 6/6] svcrdma: Make svc_rdma_send_error_msg() a global function 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=20200622205906.2144.43930.stgit@klimt.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).