linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: trond.myklebust@primarydata.com, anna.schumaker@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] Trace point improvements for sunrpc
Date: Fri, 16 Mar 2018 10:33:39 -0400	[thread overview]
Message-ID: <20180316142858.14289.44885.stgit@manet.1015granger.net> (raw)

Hi -

A clean-up and a couple of new trace point sites for client-side
sunrpc:

 - A trace point that reports the mountstats latency tuple, but
   for each RPC instead of average latency over many RPCs

 - A trace point that reports the result of RPC ping

Would you consider taking these for v4.17 ?

---

Chuck Lever (3):
      sunrpc: Simplify synopsis of some trace points
      sunrpc: Add static trace point to report RPC latency stats
      sunrpc: Add static trace point to report result of RPC ping


 include/trace/events/sunrpc.h |  106 ++++++++++++++++++++++++++++++++++-------
 net/sunrpc/clnt.c             |    8 +++
 net/sunrpc/sched.c            |   10 ++--
 net/sunrpc/stats.c            |   16 ++++--
 4 files changed, 110 insertions(+), 30 deletions(-)

--
Chuck Lever

             reply	other threads:[~2018-03-16 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 14:33 Chuck Lever [this message]
2018-03-16 14:33 ` [PATCH 1/3] sunrpc: Simplify synopsis of some trace points Chuck Lever
2018-03-16 14:33 ` [PATCH 2/3] sunrpc: Add static trace point to report RPC latency stats Chuck Lever
2018-03-16 14:33 ` [PATCH 3/3] sunrpc: Add static trace point to report result of RPC ping 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=20180316142858.14289.44885.stgit@manet.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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).