Re: [PATCH 06/17] writeback: sync expired inodes first in backgroundwriteback

[Rik van Riel]

On 05/05/2011 11:08 PM, Wu Fengguang wrote:
> A background flush work may run for ever. So it's reasonable for it to
> mimic the kupdate behavior of syncing old/expired inodes first.
>
> At each queue_io() time, first try enqueuing only newly expired inodes.
> If there are zero expired inodes to work with, then relax the rule and
> enqueue all dirty inodes.
>
> CC: Dave Chinner<david@xxxxxxxxxxxxx>
> CC: Jan Kara<jack@xxxxxxx>
> CC: Rik van Riel<riel@xxxxxxxxxx>
> Acked-by: Mel Gorman<mel@xxxxxxxxx>
> Signed-off-by: Wu Fengguang<fengguang.wu@xxxxxxxxx>

Acked-by: Rik van Riel<riel@xxxxxxxxxx>

--
All rights reversed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/