From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/2] SUNRPC: Added Tracing Points
Date: Tue, 24 Jan 2012 15:51:45 -0500 [thread overview]
Message-ID: <1327438307-2910-1-git-send-email-steved@redhat.com> (raw)
This series combines the trace points that Trond
posted, than now handle strings properly, and the
trace points I posted, in which I integrated the
review comments.
All these trace point were tested/enable through the
debugfs interface as well as being called from a
systemtab prob.
Steve Dickson (1):
SUNRPC: Adding status trace points
Trond Myklebust (1):
SUNRPC: Add trace events to the sunrpc subsystem
include/linux/sunrpc/sched.h | 2 +-
include/trace/events/sunrpc.h | 177 +++++++++++++++++++++++++++++++++++++++++
net/sunrpc/clnt.c | 6 +-
net/sunrpc/sched.c | 12 +++
4 files changed, 195 insertions(+), 2 deletions(-)
create mode 100644 include/trace/events/sunrpc.h
next reply other threads:[~2012-01-24 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 20:51 Steve Dickson [this message]
2012-01-24 20:51 ` [PATCH v3 1/2] SUNRPC: Add trace events to the sunrpc subsystem Steve Dickson
2012-01-24 20:51 ` [PATCH v2 2/2] SUNRPC: Adding status trace points Steve Dickson
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=1327438307-2910-1-git-send-email-steved@redhat.com \
--to=steved@redhat.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).