From: Jens Axboe <jens.axboe@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
rostedt@goodmis.org, fweisbec@gmail.com, acme@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: blktrace ftrace plugin, was Re: Receive side performance issue with multi-10-GigE and NUMA
Date: Thu, 27 Aug 2009 07:26:28 +0200 [thread overview]
Message-ID: <20090827052628.GE12579@kernel.dk> (raw)
In-Reply-To: <20090827003047.GA30341@infradead.org>
On Wed, Aug 26 2009, Christoph Hellwig wrote:
> On Wed, Aug 26, 2009 at 10:40:27PM +0200, Ingo Molnar wrote:
> > We are also converting non-trivial plugins to generic tracepoints. A
> > recent example are the system call tracepoints, but we also
> > converted blktrace and kmemtrace to generic tracepoints.
>
> On something semi-related: Any reason to keep the blktrace ftrace
> plugin around? I don't think there's much point in it. It only got
> added in 2.6.29, and all the blktrace tooling just uses the legacy
> ioctls. All new uses should just use the TRACE_EVENT output.
Lets kill it.
--
Jens Axboe
next prev parent reply other threads:[~2009-08-27 5:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090826181502.GC13632@elte.hu>
[not found] ` <20090826190435.GC10816@hmsreliant.think-freely.org>
[not found] ` <20090826190830.GF13632@elte.hu>
[not found] ` <20090826.123631.79533250.davem@davemloft.net>
[not found] ` <20090826194835.GA16508@elte.hu>
[not found] ` <20090826202344.GE10816@hmsreliant.think-freely.org>
[not found] ` <20090826204027.GA21159@elte.hu>
2009-08-27 0:30 ` blktrace ftrace plugin, was Re: Receive side performance issue with multi-10-GigE and NUMA Christoph Hellwig
2009-08-27 5:26 ` Jens Axboe [this message]
2009-08-27 9:12 ` Ingo Molnar
2009-08-27 9:14 ` Jens Axboe
2009-08-27 13:55 ` Arnaldo Carvalho de Melo
2009-08-28 2:03 ` Li Zefan
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=20090827052628.GE12579@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--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