linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] ftrace interface for blktrace
Date: Sat, 17 Jan 2009 20:14:30 +0100	[thread overview]
Message-ID: <20090117191430.GA30821@kernel.dk> (raw)
In-Reply-To: <20090117190913.GA17722@elte.hu>

On Sat, Jan 17 2009, Ingo Molnar wrote:
> 
> * Arnaldo Carvalho de Melo <acme@redhat.com> wrote:
> 
> > Hi Jens,
> > 
> > 	The patch below adds a ftrace interface for blktrace, allowing 
> > people to use it without any required userspace tools, using sysfs to 
> > setup the act_mask, pid, start_lba, end_lba.
> 
> Very nice patch!
> 
> Jens, i'm wondering what's your take on this direction is. I think the 
> consolidation effect is great and the built-in IO tracing capabilities are 
> very nice.

I like the current patch, from a quick look. I'll look more soonish
(monday). I've always liked the concept of being able to mix various
traces into the same stream, since it makes it MUCH easier to see what
on earth is going wrong. What I didn't like in the patches Acme did was
the enable part, I'll need to look into that. Again, from a quick look,
what is the BKL doing in there?!

> We can still get the raw events too and do user-space post-processing, 
> when that is desired - so this does not limit anything that blktrace was 
> able to do before - it only extends on it.
> 
> Is there any particular blktrace feature you can think of that is not 
> present in the blktrace ftrace plugin?

Can't answer that yet, I'll give it a more thorough look next week.

-- 
Jens Axboe


  reply	other threads:[~2009-01-17 19:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 18:16 [RFC][PATCH] ftrace interface for blktrace Arnaldo Carvalho de Melo
2009-01-16 19:15 ` Steven Rostedt
2009-01-16 19:41   ` Arnaldo Carvalho de Melo
2009-01-17 13:37 ` Frederic Weisbecker
2009-01-17 20:22   ` Arnaldo Carvalho de Melo
2009-01-19 13:33     ` Ingo Molnar
2009-01-17 19:09 ` Ingo Molnar
2009-01-17 19:14   ` Jens Axboe [this message]
2009-01-17 20:08     ` Arnaldo Carvalho de Melo
2009-01-20 14:42       ` [RFC][PATCHv2] " Arnaldo Carvalho de Melo
2009-01-20 17:03         ` Steven Rostedt
2009-01-20 17:58           ` Arnaldo Carvalho de Melo
2009-01-20 18:23             ` Arnaldo Carvalho de Melo
2009-01-20 23:23         ` Frederic Weisbecker

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=20090117191430.GA30821@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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).