writeback: Include all dirty inodes in background writeback
authorJan Kara <jack@suse.cz>
Wed, 19 Oct 2011 09:44:41 +0000 (11:44 +0200)
committerWu Fengguang <fengguang.wu@intel.com>
Sun, 18 Dec 2011 06:20:18 +0000 (14:20 +0800)
commit1bc36b6426ae49139e9f56491db76b95921454d7
tree66708091d7628c45cb81279dcdefd911b11aa3e1
parentb3bba872ddb0320a7ecb54decae53c13ceb2ed4c
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>
fs/fs-writeback.c