This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [PATCH] Add tracepoints to track pagecache transition
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Atsushi Tsuji <a-tsuji at bk dot jp dot nec dot com>
- Cc: mathieu dot desnoyers at polymtl dot ca, ltt-dev at lists dot casi dot polymtl dot ca, systemtap at sources dot redhat dot com, Kazuto Miyoshi <miyoshi at linux dot bs1 dot fc dot nec dot co dot jp>
- Date: Wed, 04 Feb 2009 19:48:51 -0500
- Subject: Re: [PATCH] Add tracepoints to track pagecache transition
- References: <4987DF60.9030504@bk.jp.nec.com>
Atsushi Tsuji <a-tsuji@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