From: Christoph Hellwig <hch@infradead.org>
To: Curt Wohlgemuth <curtw@google.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Wu Fengguang <fengguang.wu@intel.com>, Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
Michael Rubin <mrubin@google.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: Writeback tests
Date: Fri, 15 Jul 2011 19:44:23 -0400 [thread overview]
Message-ID: <20110715234423.GA10296@infradead.org> (raw)
In-Reply-To: <CAO81RMYv1=aHcOtPZdYoafcz-f_w-9JNan8rb7OMyxkGOMXWBg@mail.gmail.com>
On Fri, Jul 15, 2011 at 04:41:38PM -0700, Curt Wohlgemuth wrote:
> $ cat /proc/writeback/stats
> call: balance_dirty_pages 2253
> call: background_writeout 45
> call: try_to_free_pages 0
> call: sync 14
> call: kupdate 228
> call: shrink_page_list 0
> call: fdatawrite 6755
> call: laptop_periodic 0
> call: free_more_memory 0
> page: balance_dirty_pages 455830
> page: background_writeout 391568
> page: try_to_free_pages 0
> page: sync 133
> page: kupdate 1158779
> page: shrink_page_list 0
> page: fdatawrite 777320
> page: laptop_periodic 0
> page: free_more_memory 0
> periodic writeback 241
> single inode wait 0
> writeback_wb wait 7
> metadata pages cleaned 19473
A fair amount of the page stats should be provided by Wu and Jan's
recent patches, shouldn't they? I don't think the calls stats
are such a good idea. We can triviall get these stats by using
perf - just place a probe at the function and then count it using
perf record.
But if would be good to get the remaining page stats in, as they
seems pretty useful.
next prev parent reply other threads:[~2011-07-15 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 22:52 Writeback tests Curt Wohlgemuth
2011-07-15 15:33 ` Christoph Hellwig
2011-07-15 23:41 ` Curt Wohlgemuth
2011-07-15 23:44 ` Christoph Hellwig [this message]
2011-07-19 16:46 ` Curt Wohlgemuth
2011-07-20 21:49 ` Curt Wohlgemuth
2011-08-10 16:54 ` 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=20110715234423.GA10296@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=curtw@google.com \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mrubin@google.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;
as well as URLs for NNTP newsgroup(s).