On Mon, 27 Aug 2007 05:03:36 -0700
Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> On Mon, 27 Aug 2007 19:21:52 +0800
> >
> > Because it does the work in small batches of 10 inodes, when the
> > system has <=10 dirty inodes, its behavior will reduce to:
> > - do a full sweep *at once* on every 25s
On Mon, Aug 27, 2007 at 05:03:36AM -0700, Arjan van de Ven wrote:
> On Mon, 27 Aug 2007 19:21:52 +0800
> >
> > Because it does the work in small batches of 10 inodes, when the
> > system has <=10 dirty inodes, its behavior will reduce to:
> > - do a full sweep *at once* on every 25s
> > Which mean
On Mon, 27 Aug 2007 19:21:52 +0800
>
> Because it does the work in small batches of 10 inodes, when the
> system has <=10 dirty inodes, its behavior will reduce to:
> - do a full sweep *at once* on every 25s
> Which means the disk will flicker once every 25s, not bad :)
25 seconds is quite not go
Chris,
This is one possible implementation of the clustered writeback idea.
It runs OK on ext3 (compiling, syncing, etc.).
The patch is based on 2.6.23-rc3-mm1 and the writeback patches here:
http://lkml.org/lkml/2007/8/19/10
By default, with many dirty inodes, it works as follows:
- store dirty
4 matches
Mail list logo