On Mon, Jul 19, 2010 at 10:21:45AM -0400, Christoph Hellwig wrote: > On Mon, Jul 19, 2010 at 02:11:29PM +0100, Mel Gorman wrote: > > From: Wu Fengguang <fengguang.wu@xxxxxxxxx> > > > > 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. > > > > This behavior also makes sense from the perspective of page reclaim. > > File pages are added to the inactive list and promoted if referenced > > after one recycling. If not referenced, it's very easy for pages to be > > cleaned from reclaim context which is inefficient in terms of IO. If > > background flush is cleaning pages, it's best it cleans old pages to > > help minimise IO from reclaim. > > Yes, we absolutely do this. Do you mean we absolutely want to do this? > Wu, do you have an improved version of the > pending or should we put it in this version for now? > Some insight on how the other writeback changes that are being floated around might affect the number of dirty pages reclaim encounters would also be helpful. The tracepoints are there for people to figure it out but any help figuring it out is useful. -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
