writeback: Include all dirty inodes in background writeback
Current livelock avoidance code makes background work to include only inodes that were dirtied before background writeback has started. However background writeback can be running for a long time and thus excluding newly dirtied inodes can eventually exclude significant portion of dirty inodes making background writeback inefficient. Since background writeback avoids livelocking the flusher thread by yielding to any other work, there is no real reason why background work should not include all dirty inodes so change the logic in wb_writeback(). Signed-off-by:Jan Kara <jack@suse.cz> Signed-off-by:
Wu Fengguang <fengguang.wu@intel.com>
parent
b3bba872
Please register or sign in to comment