[Top] [All Lists]

Re: buffered writeback torture program

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: buffered writeback torture program
From: Chris Mason <chris.mason@xxxxxxxxxx>
Date: Thu, 21 Apr 2011 14:29:37 -0400
Cc: Andreas Dilger <adilger@xxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, linux-ext4 <linux-ext4@xxxxxxxxxxxxxxx>, xfs <xfs@xxxxxxxxxxx>, jack <jack@xxxxxxx>, axboe <axboe@xxxxxxxxx>, dchinner <dchinner@xxxxxxxxxx>
In-reply-to: <20110421180805.GA2627@xxxxxxxxxxxxx>
References: <1303322378-sup-1722@think> <20110421083258.GA26784@xxxxxxxxxxxxx> <1303407205-sup-6141@think> <20110421174120.GA7267@xxxxxxxxxxxxx> <93CB867E-B908-4B38-A146-A9DC958ACF64@xxxxxxxxx> <20110421180213.GA19255@xxxxxxxxxxxxx> <1303408883-sup-1495@think> <20110421180805.GA2627@xxxxxxxxxxxxx>
User-agent: Sup/git
Excerpts from Christoph Hellwig's message of 2011-04-21 14:08:05 -0400:
> On Thu, Apr 21, 2011 at 02:02:43PM -0400, Chris Mason wrote:
> > For this program, they are almost all dirty pages.
> > 
> > I tried patching it to give up if we seek but it is still pretty slow.
> > There's something else going on in addition to the xfs clustering being
> > too aggressive.
> I'm not sure where you this beeing to agressive from - it's doing
> exactly the same amount of I/O as a filesystem writing out a single
> page from ->writepage or using write_cache_pages (either directly
> or as a copy) as ->writepages.  The only thing special compared to
> the no ->writepages case is that it's submitting a large I/O
> from the first ->writepage call.

Ok, I see what you mean.  The clustering code stops once it hits
nr_to_write, I missed that.  So we shouldn't be doing more than a single
writepages call.


<Prev in Thread] Current Thread [Next in Thread>