From: Wu Fengguang <fengguang.wu@intel.com>
To: "Li, Shaohua" <shaohua.li@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"richard@rsk.demon.co.uk" <richard@rsk.demon.co.uk>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
"jens.axboe@oracle.com" <jens.axboe@oracle.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: regression in page writeback
Date: Tue, 22 Sep 2009 21:39:04 +0800 [thread overview]
Message-ID: <20090922133904.GA9967@localhost> (raw)
In-Reply-To: <20090922115015.GB6175@sli10-desk.sh.intel.com>
On Tue, Sep 22, 2009 at 07:50:15PM +0800, Li, Shaohua wrote:
> On Tue, Sep 22, 2009 at 06:49:15PM +0800, Wu, Fengguang wrote:
> > Shaohua,
> >
> > On Tue, Sep 22, 2009 at 01:49:13PM +0800, Li, Shaohua wrote:
> > > Hi,
> > > Commit d7831a0bdf06b9f722b947bb0c205ff7d77cebd8 causes disk io regression
> > > in my test.
> > > My system has 12 disks, each disk has two partitions. System runs fio sequence
> > > write on all partitions, each partion has 8 jobs.
> > > 2.6.31-rc1, fio gives 460m/s disk io
> > > 2.6.31-rc2, fio gives about 400m/s disk io. Revert the patch, speed back to
> > > 460m/s
> > >
> > > Under latest git: fio gives 450m/s disk io; If reverting the patch, the speed
> > > is 484m/s.
> > >
> > > With the patch, fio reports less io merge and more interrupts. My naive
> > > analysis is the patch makes balance_dirty_pages_ratelimited_nr() limits
> > > write chunk to 8 pages and then soon go to sleep in balance_dirty_pages(),
> > > because most time the bdi_nr_reclaimable < bdi_thresh, and so when write
> > > the pages out, the chunk is 8 pages long instead of 4M long. Without the patch,
> > > thread can write 8 pages and then move some pages to writeback, and then
> > > continue doing write. The patch seems to break this.
> >
> > Do you have trace/numbers for above descriptions?
> No. Just guess, because there is less io merge. And watch each bdi's states,
> bdi_nr_reclaimable < bdi_thresh seems always true.
Ah OK.
> > > Unfortunatelly I can't figure out a fix for this issue, hopefully
> > > you have more ideas.
> >
> > Attached is a very verbose writeback debug patch, hope it helps and
> > won't disturb the workload a lot :)
> Hmm, the log buf will get overflowed soon, there is > 400m/s io. I tried
> to produce this issue in a system with two disks, but fail. Anyway, I'll try
> it out tomorrow.
Thank you~ I'd recommend to use netconsole or serial line, and stop
local klogd because the write of log messages could add noises.
Thanks,
Fengguang
next prev parent reply other threads:[~2009-09-22 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090922054913.GA27260@sli10-desk.sh.intel.com>
[not found] ` <1253601612.8439.274.camel@twins>
[not found] ` <20090922080505.GB9192@localhost>
[not found] ` <1253606965.8439.281.camel@twins>
[not found] ` <20090922082427.GA24888@localhost>
[not found] ` <1253608335.8439.283.camel@twins>
2009-09-22 8:51 ` regression in page writeback Wu Fengguang
2009-09-22 10:49 ` Wu Fengguang
2009-09-22 11:50 ` Shaohua Li
2009-09-22 13:39 ` Wu Fengguang [this message]
2009-09-23 1:52 ` Shaohua Li
2009-09-23 4:00 ` Wu Fengguang
2009-09-25 6:14 ` Wu Fengguang
[not found] <20090922182832.28e7f73a.akpm@linux-foundation.org>
[not found] ` <20090923014500.GA11076@localhost>
[not found] ` <20090922185941.1118e011.akpm@linux-foundation.org>
[not found] ` <20090923022622.GB11918@localhost>
[not found] ` <20090922193622.42c00012.akpm@linux-foundation.org>
[not found] ` <20090923140058.GA2794@think>
[not found] ` <20090924031508.GD6456@localhost>
[not found] ` <20090925001117.GA9464@discord.disaster>
[not found] ` <20090925031920.GB10487@localhost>
[not found] ` <20090926014715.GD9464@discord.disaster>
2009-09-26 3:02 ` Wu Fengguang
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=20090922133904.GA9967@localhost \
--to=fengguang.wu@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@rsk.demon.co.uk \
--cc=shaohua.li@intel.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).