From: fche@redhat.com (Frank Ch. Eigler)
Subject: [ltt-dev] [PATCH] Add tracepoints to track pagecache transition
Date: Wed, 04 Feb 2009 19:48:51 -0500 [thread overview]
Message-ID: <y0m1vudogi4.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <4987DF60.9030504@bk.jp.nec.com> (Atsushi Tsuji's message of "Tue, 03 Feb 2009 15:08:32 +0900")
Atsushi Tsuji <a-tsuji at bk.jp.nec.com> writes:
> I thought it would be useful to trace pagecache behavior for problem
> analysis (performance bottlenecks, behavior differences between stable
> time and trouble time).
Interesting! I hope it inspires more thinking about more places and
ways for graphical data visualization to apply.
> By using those tracepoints, we can describe and visualize pagecache
> transition (file-by-file basis) in kernel and pagecache consumes
> most of the memory in running system and pagecache hit rate and
> writeback behavior will influence system load and performance.
To what extent does your script work if it uses kprobes-based
kernel.function() probes? (It can use "!" type probe point
decorations to automatically adapt to the preferred presence of the
tracepoints/markers.)
> I attached an example which is visualization of pagecache status
> using SystemTap. [...]
Would you consider sharing this script?
- FChE
next prev parent reply other threads:[~2009-02-05 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 6:08 Atsushi Tsuji
2009-02-03 14:07 ` Mathieu Desnoyers
2009-02-03 14:16 ` Mathieu Desnoyers
2009-02-04 1:07 ` Atsushi Tsuji
2009-02-04 5:56 ` Mathieu Desnoyers
2009-02-05 0:48 ` Frank Ch. Eigler [this message]
2009-02-09 2:54 ` Atsushi Tsuji
2009-02-11 7:18 ` Mathieu Desnoyers
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=y0m1vudogi4.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
/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