From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jens Axboe <jens.axboe@oracle.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] ftrace interface for blktrace
Date: Mon, 19 Jan 2009 14:33:58 +0100 [thread overview]
Message-ID: <20090119133358.GE23299@elte.hu> (raw)
In-Reply-To: <20090117202247.GK6562@ghostprotocols.net>
* Arnaldo Carvalho de Melo <acme@redhat.com> wrote:
> I hope that by dropping the requirement to a userspace bit (be it big or
> small) we can set a record for such kind of tracing infrastructure now
> that tracepoints are being proposed left and right.
>
> After all, somebody said that userspace is just a test case for the
> kernel, and for things like developer assists...
Exactly.
Also, for certain tracing modes where we just do the run to gather
statistics (but do not plan to capture any trace), it is more efficient to
have an in-kernel histogram than to export gobs of data to user-space at
great expense, just to throw away most of it there ;-)
Ingo
next prev parent reply other threads:[~2009-01-19 13:34 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 [this message]
2009-01-17 19:09 ` Ingo Molnar
2009-01-17 19:14 ` Jens Axboe
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=20090119133358.GE23299@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.