From: Wu Fengguang <fengguang.wu@intel.com>
To: Curt Wohlgemuth <curtw@google.com>
Cc: Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
Michael Rubin <mrubin@google.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 2/2 v2] writeback: Add writeback stats for pages written
Date: Tue, 16 Aug 2011 20:26:54 +0800 [thread overview]
Message-ID: <20110816122654.GB13391@localhost> (raw)
In-Reply-To: <CAO81RMbe=ht0H_Ut9ybATKZFV7KFDBP8oT1_ZHz-Ve87gcvq2A@mail.gmail.com>
Curt,
> > The above stats are probably useful. I'm not so convinced about the stats
> > below - it looks like it should be simple enough to get them by enabling
> > some trace points and processing output (or if we are missing some
> > tracepoints, it would be worthwhile to add them).
>
> For these specifically, I'd agree with you. In general, though, I
> think that having generally available aggregated stats is really
> useful, in a different way than tracepoints are.
If there comes such useful aggregated stats in future, they may go to
vmstat and/or /debug/bdi/<dev>/stats.
Then we make the writeback stats a simple uniform interface rather
than a hybrid one.
> >
> >> periodic writeback 377
The above one can go to the "work" column, "periodic" row of the
writeback stats table :)
I'm in particular interested in the "work" column of the
"try_to_free_pages" row. I also suspect there could be many
short-lived background work, hence there lots of them.
> >> single inode wait 0
> >> writeback_wb wait 1
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu@intel.com>
To: Curt Wohlgemuth <curtw@google.com>
Cc: Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
Michael Rubin <mrubin@google.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 2/2 v2] writeback: Add writeback stats for pages written
Date: Tue, 16 Aug 2011 20:26:54 +0800 [thread overview]
Message-ID: <20110816122654.GB13391@localhost> (raw)
In-Reply-To: <CAO81RMbe=ht0H_Ut9ybATKZFV7KFDBP8oT1_ZHz-Ve87gcvq2A@mail.gmail.com>
Curt,
> > A The above stats are probably useful. I'm not so convinced about the stats
> > below - it looks like it should be simple enough to get them by enabling
> > some trace points and processing output (or if we are missing some
> > tracepoints, it would be worthwhile to add them).
>
> For these specifically, I'd agree with you. In general, though, I
> think that having generally available aggregated stats is really
> useful, in a different way than tracepoints are.
If there comes such useful aggregated stats in future, they may go to
vmstat and/or /debug/bdi/<dev>/stats.
Then we make the writeback stats a simple uniform interface rather
than a hybrid one.
> >
> >> A A periodic writeback A A A A A A A A A A A 377
The above one can go to the "work" column, "periodic" row of the
writeback stats table :)
I'm in particular interested in the "work" column of the
"try_to_free_pages" row. I also suspect there could be many
short-lived background work, hence there lots of them.
> >> A A single inode wait A A A A A A A A A A A A 0
> >> A A writeback_wb wait A A A A A A A A A A A A 1
Thanks,
Fengguang
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-16 12:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 22:47 [PATCH 1/2 v2] writeback: Add a 'reason' to wb_writeback_work Curt Wohlgemuth
2011-08-12 22:47 ` Curt Wohlgemuth
2011-08-12 22:47 ` [PATCH 2/2 v2] writeback: Add writeback stats for pages written Curt Wohlgemuth
2011-08-12 22:47 ` Curt Wohlgemuth
2011-08-15 13:48 ` Wu Fengguang
2011-08-15 13:48 ` Wu Fengguang
2011-08-15 17:16 ` Curt Wohlgemuth
2011-08-15 17:16 ` Curt Wohlgemuth
2011-08-15 18:40 ` Jan Kara
2011-08-15 18:40 ` Jan Kara
2011-08-15 18:56 ` Curt Wohlgemuth
2011-08-15 18:56 ` Curt Wohlgemuth
2011-08-16 13:10 ` Jan Kara
2011-08-16 13:10 ` Jan Kara
2011-08-16 12:10 ` Wu Fengguang
2011-08-15 15:03 ` Jan Kara
2011-08-15 15:03 ` Jan Kara
2011-08-15 17:24 ` Curt Wohlgemuth
2011-08-16 12:26 ` Wu Fengguang [this message]
2011-08-16 12:26 ` Wu Fengguang
2011-08-15 13:19 ` [PATCH 1/2 v2] writeback: Add a 'reason' to wb_writeback_work Wu Fengguang
2011-08-15 13:19 ` Wu Fengguang
2011-09-28 15:02 ` Christoph Hellwig
2011-09-28 15:02 ` Christoph Hellwig
2011-10-07 15:28 ` Wu Fengguang
2011-10-07 18:07 ` Curt Wohlgemuth
2011-10-07 18:07 ` Curt Wohlgemuth
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=20110816122654.GB13391@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=curtw@google.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.