writeback: moving expire targets for background/kupdate works
From: | Wu Fengguang <fengguang.wu@intel.com> | |
To: | Andrew Morton <akpm@linux-foundation.org> | |
Subject: | [PATCH 0/6] writeback: moving expire targets for background/kupdate works | |
Date: | Tue, 19 Apr 2011 11:00:03 +0800 | |
Message-ID: | <20110419030003.108796967@intel.com> | |
Cc: | Jan Kara <jack@suse.cz>, Mel Gorman <mel@linux.vnet.ibm.com> | |
Archive‑link: | Article |
Andrew, This aims to reduce possible pageout() calls by making the flusher concentrate a bit more on old/expired dirty inodes. Patches 04, 05 have been updated since last post, please review. The concerns from last review have been addressed. It runs fine on simple workloads over ext3/4, xfs, btrfs and NFS. Trond, will you take the last patch? The fixed "bug" has no real impact for now. make dirty expire time a moving target [PATCH 1/6] writeback: pass writeback_control down to move_expired_inodes() [PATCH 2/6] writeback: the kupdate expire timestamp should be a moving target [PATCH 3/6] writeback: sync expired inodes first in background writeback loop condition fixes (the most tricky part) [PATCH 4/6] writeback: introduce writeback_control.inodes_cleaned [PATCH 5/6] writeback: try more writeback as long as something was written NFS fix [PATCH 6/6] NFS: return -EAGAIN when skipped commit in nfs_commit_unstable_pages() Thanks, Fengguang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/