From: Vaibhav Nagarnaik <vnagarnaik@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Ingo Molnar <mingo@redhat.com>, Michael Rubin <mrubin@google.com>,
David Sharp <dhsharp@google.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, Jiaying Zhang <jiayingz@google.com>
Subject: Re: [PATCH] trace: Add tracepoints to fs subsystem
Date: Mon, 25 Apr 2011 16:52:05 -0700 [thread overview]
Message-ID: <BANLkTimochpX5Tzvj0Yz6Lb+3-tcFuZXqQ@mail.gmail.com> (raw)
In-Reply-To: <1303745985.18763.14.camel@gandalf.stny.rr.com>
On Mon, Apr 25, 2011 at 8:39 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 2011-04-25 at 11:35 +0900, KOSAKI Motohiro wrote:
>> > From: Jiaying Zhang <jiayingz@google.com>
>> >
>> > Many fs tracepoints can now be traced via ftrace, however there are a
>> > few other tracepoints needed. This patch adds entry and exit tracepoints
>> > for a few additional functions, viz.:
>> > wait_on_buffer
>> > block_write_full_page
>> > mpage_readpages
>> > file_read
>>
>> Zero background description?
>>
>
> Good point.
>
> Could you please describe how this is useful, and how one can benefit
> from these tracepoints.
>
I am sending a new patch with a better description and using the template for
declaring events.
> -- Steve
>
>
>
>
Thanks
Vaibhav Nagarnaik
next prev parent reply other threads:[~2011-04-25 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 23:00 [PATCH] trace: Add tracepoints to fs subsystem Vaibhav Nagarnaik
2011-04-25 2:35 ` KOSAKI Motohiro
2011-04-25 15:39 ` Steven Rostedt
2011-04-25 23:52 ` Vaibhav Nagarnaik [this message]
2011-04-25 15:38 ` Steven Rostedt
2011-04-25 23:53 ` Vaibhav Nagarnaik
2011-04-28 23:16 ` Vaibhav Nagarnaik
2011-06-14 0:42 ` Vaibhav Nagarnaik
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=BANLkTimochpX5Tzvj0Yz6Lb+3-tcFuZXqQ@mail.gmail.com \
--to=vnagarnaik@google.com \
--cc=dhsharp@google.com \
--cc=jiayingz@google.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=mrubin@google.com \
--cc=rostedt@goodmis.org \
--cc=viro@zeniv.linux.org.uk \
/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).