From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: [PATCH v1 0/6] Server-side completion IDs
Date: Mon, 29 Jun 2020 10:58:33 -0400 [thread overview]
Message-ID: <20200629145528.15100.77805.stgit@klimt.1015granger.net> (raw)
I'd like to remove the display and storage of kernel memory
addresses from the RPC/RDMA transport's tracepoints. This reduces
the size of trace records and closes a (possibly minor) security
exposure.
This series is a down payment on that effort. A similar series is
in the works for the client side transport implementation.
---
Chuck Lever (6):
svcrdma: Introduce infrastructure to support completion IDs
svcrdma: Introduce Receive completion IDs
svcrdma: Record Receive completion ID in svc_rdma_decode_rqst
svcrdma: Introduce Send completion IDs
svcrdma: Record send_ctxt completion ID in trace_svcrdma_post_send()
svcrdma: Display chunk completion ID when posting a rw_ctxt
include/linux/sunrpc/svc_rdma.h | 9 +-
include/trace/events/rpcrdma.h | 161 +++++++++------------
net/sunrpc/xprtrdma/svc_rdma_backchannel.c | 2 +-
net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 27 ++--
net/sunrpc/xprtrdma/svc_rdma_rw.c | 14 +-
net/sunrpc/xprtrdma/svc_rdma_sendto.c | 26 +++-
6 files changed, 128 insertions(+), 111 deletions(-)
--
Chuck Lever
next reply other threads:[~2020-06-29 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 14:58 Chuck Lever [this message]
2020-06-29 14:58 ` [PATCH v1 1/6] svcrdma: Introduce infrastructure to support completion IDs Chuck Lever
2020-06-29 14:58 ` [PATCH v1 2/6] svcrdma: Introduce Receive " Chuck Lever
2020-06-29 14:58 ` [PATCH v1 3/6] svcrdma: Record Receive completion ID in svc_rdma_decode_rqst Chuck Lever
2020-06-29 14:58 ` [PATCH v1 4/6] svcrdma: Introduce Send completion IDs Chuck Lever
2020-06-29 14:59 ` [PATCH v1 5/6] svcrdma: Record send_ctxt completion ID in trace_svcrdma_post_send() Chuck Lever
2020-06-29 14:59 ` [PATCH v1 6/6] svcrdma: Display chunk completion ID when posting a rw_ctxt 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=20200629145528.15100.77805.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).