From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org
Subject: [PATCH RFC 0/5] Ideas for new NFS and RPC trace points
Date: Fri, 25 Jan 2019 17:07:22 -0500 [thread overview]
Message-ID: <154845390550.70638.13083502621745566898.stgit@seurat.1015granger.net> (raw)
Here are some trace point-related changes that could improve the
observability of NFS and RPC operation. Interested in comments.
---
Chuck Lever (5):
SUNRPC: Add xdr_stream::rqst field
SUNRPC: Add XDR overflow trace event
SUNRPC: Add trace event that reports reply page vector alignment
NFS: Remove print_overflow_msg()
NFS: Add trace events to report non-zero NFS status codes
fs/lockd/clnt4xdr.c | 14 -
fs/lockd/clntxdr.c | 14 -
fs/nfs/callback_xdr.c | 64 ++--
fs/nfs/flexfilelayout/flexfilelayout.c | 2
fs/nfs/nfs2xdr.c | 91 ++----
fs/nfs/nfs3xdr.c | 170 ++++--------
fs/nfs/nfs42xdr.c | 21 -
fs/nfs/nfs4trace.h | 25 ++
fs/nfs/nfs4xdr.c | 463 +++++++++-----------------------
fs/nfs/nfstrace.c | 1
fs/nfs/nfstrace.h | 85 ++++++
fs/nfsd/nfs4callback.c | 13 -
include/linux/sunrpc/xdr.h | 8 -
include/trace/events/sunrpc.h | 126 +++++++++
net/sunrpc/auth.c | 4
net/sunrpc/auth_gss/auth_gss.c | 4
net/sunrpc/xdr.c | 69 ++++-
net/sunrpc/xprtrdma/backchannel.c | 2
net/sunrpc/xprtrdma/rpc_rdma.c | 4
19 files changed, 548 insertions(+), 632 deletions(-)
--
Chuck Lever
next reply other threads:[~2019-01-25 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 22:07 Chuck Lever [this message]
2019-01-25 22:08 ` [PATCH RFC 1/5] SUNRPC: Add xdr_stream::rqst field Chuck Lever
2019-01-25 22:08 ` [PATCH RFC 2/5] SUNRPC: Add XDR overflow trace event Chuck Lever
2019-01-25 22:09 ` [PATCH RFC 3/5] SUNRPC: Add trace event that reports reply page vector alignment Chuck Lever
2019-01-25 22:10 ` [PATCH RFC 4/5] NFS: Remove print_overflow_msg() Chuck Lever
2019-01-25 22:11 ` [PATCH RFC 5/5] NFS: Add trace events to report non-zero NFS status codes 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=154845390550.70638.13083502621745566898.stgit@seurat.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@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).