On Mon, Nov 1, 2010 at 9:22 PM, Wu Fengguang <fengguang.wu@xxxxxxxxx> wrote: > From: Jan Kara <jack@xxxxxxx> > > Background writeback are easily livelockable (from a definition of their > target). This is inconvenient because it can make sync(1) stall forever waiting > on its queued work to be finished. Generally, when a flusher thread has > some work queued, someone submitted the work to achieve a goal more specific > than what background writeback does. So it makes sense to give it a priority > over a generic page cleaning. > > Thus we interrupt background writeback if there is some other work to do. We > return to the background writeback after completing all the queued work. > > Signed-off-by: Jan Kara <jack@xxxxxxx> > Signed-off-by: Wu Fengguang <fengguang.wu@xxxxxxxxx> Reviewed-by: Minchan Kim <minchan.kim@xxxxxxxxx> -- Kind regards, Minchan Kim -- 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
