From: Chuck Lever <chuck.lever@oracle.com>
To: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v1 0/7] svcrdma observability improvements
Date: Fri, 01 May 2020 13:40:26 -0400 [thread overview]
Message-ID: <20200501173903.3899.31567.stgit@klimt.1015granger.net> (raw)
Hi-
(cc: linux-rdma and linux-nfs)
These are minor clean-ups in the svcrdma code that I found while
addressing other issues.
---
Chuck Lever (7):
svcrdma: Clean up the tracing for rw_ctx_init errors
svcrdma: Clean up handling of get_rw_ctx errors
svcrdma: Trace page overruns when constructing RDMA Reads
svcrdma: trace undersized Write chunks
svcrdma: Fix backchannel return code
svcrdma: Remove backchannel dprintk call sites
svcrdma: Rename tracepoints that record header decoding errors
include/linux/sunrpc/svc_rdma.h | 5 +-
include/trace/events/rpcrdma.h | 90 +++++++++++++++++++++-
net/sunrpc/xprtrdma/svc_rdma_backchannel.c | 86 ++++-----------------
net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 21 +++--
net/sunrpc/xprtrdma/svc_rdma_rw.c | 36 ++++-----
5 files changed, 129 insertions(+), 109 deletions(-)
--
Chuck Lever
next reply other threads:[~2020-05-01 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 17:40 Chuck Lever [this message]
2020-05-01 17:40 ` [PATCH v1 1/7] svcrdma: Clean up the tracing for rw_ctx_init errors Chuck Lever
2020-05-01 17:40 ` [PATCH v1 2/7] svcrdma: Clean up handling of get_rw_ctx errors Chuck Lever
2020-05-01 17:40 ` [PATCH v1 3/7] svcrdma: Trace page overruns when constructing RDMA Reads Chuck Lever
2020-05-01 17:40 ` [PATCH v1 4/7] svcrdma: trace undersized Write chunks Chuck Lever
2020-05-01 17:40 ` [PATCH v1 5/7] svcrdma: Fix backchannel return code Chuck Lever
2020-05-01 17:40 ` [PATCH v1 6/7] svcrdma: Remove backchannel dprintk call sites Chuck Lever
2020-05-01 17:41 ` [PATCH v1 7/7] svcrdma: Rename tracepoints that record header decoding errors 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=20200501173903.3899.31567.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