From: Peter Zijlstra <peterz@infradead.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Atsushi Tsuji <a-tsuji@bk.jp.nec.com>,
linux-kernel@vger.kernel.org, Jason Baron <jbaron@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
Kazuto Miyoshi <miyoshi@linux.bs1.fc.nec.co.jp>,
rostedt@goodmis.org, linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Hugh Dickins <hugh@veritas.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH] Add tracepoints to track pagecache transition
Date: Tue, 17 Feb 2009 12:54:11 +0100 [thread overview]
Message-ID: <1234871651.4744.89.camel@laptop> (raw)
In-Reply-To: <20090217201651.576E.A69D9226@jp.fujitsu.com>
On Tue, 2009-02-17 at 20:38 +0900, KOSAKI Motohiro wrote:
> If you want to see I/O activity, you need to add tracepoint into block
> layer.
We already have that, Arnaldo converted blktrace to use tracepoints and
wrote an ftrace tracer for it.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-02-17 11:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <499A7CAD.9030409@bk.jp.nec.com>
2009-02-17 9:33 ` Peter Zijlstra
2009-02-17 11:04 ` Atsushi Tsuji
2009-02-17 11:38 ` KOSAKI Motohiro
2009-02-17 11:54 ` Peter Zijlstra [this message]
2009-02-17 12:33 ` KOSAKI Motohiro
2009-02-17 14:33 ` Frederic Weisbecker
2009-02-18 0:29 ` KOSAKI Motohiro
2009-02-19 4:41 ` Atsushi Tsuji
2009-02-19 13:12 ` KOSAKI Motohiro
2009-02-19 14:21 ` Lee Schermerhorn
2009-02-20 1:13 ` KOSAKI Motohiro
2009-02-17 15:24 ` Steven Rostedt
2009-02-19 18:51 ` Christoph Hellwig
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=1234871651.4744.89.camel@laptop \
--to=peterz@infradead.org \
--cc=a-tsuji@bk.jp.nec.com \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=fche@redhat.com \
--cc=hugh@veritas.com \
--cc=jbaron@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=miyoshi@linux.bs1.fc.nec.co.jp \
--cc=nickpiggin@yahoo.com.au \
--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