[PATCH 00/15] writeback fixes and cleanups for 3.0 (v5)

From: Wu Fengguang
Date: Tue Jun 07 2011 - 17:44:30 EST



Andrew,

Here are the intented patches for upstream submission, rebased to v3.0-rc2:

[PATCH 01/15] writeback: introduce .tagged_writepages for the WB_SYNC_NONE sync stage
[PATCH 02/15] writeback: update dirtied_when for synced inode to prevent livelock
[PATCH 03/15] writeback: introduce writeback_control.inodes_cleaned
[PATCH 04/15] writeback: try more writeback as long as something was written
[PATCH 05/15] writeback: the kupdate expire timestamp should be a moving target
[PATCH 06/15] writeback: refill b_io iff empty
[PATCH 07/15] writeback: split inode_wb_list_lock into bdi_writeback.list_lock
[PATCH 08/15] writeback: elevate queue_io() into wb_writeback()
[PATCH 09/15] writeback: avoid extra sync work at enqueue time
[PATCH 10/15] writeback: add bdi_dirty_limit() kernel-doc
[PATCH 11/15] writeback: skip balance_dirty_pages() for in-memory fs
[PATCH 12/15] writeback: remove writeback_control.more_io
[PATCH 13/15] writeback: remove .nonblocking and .encountered_congestion
[PATCH 14/15] writeback: trace event writeback_single_inode
[PATCH 15/15] writeback: trace event writeback_queue_io

fs/block_dev.c | 16 ++-
fs/ext4/inode.c | 4 +-
fs/fs-writeback.c | 219 ++++++++++++++++++++------------------
fs/inode.c | 5 +-
fs/nfs/write.c | 3 +-
fs/xfs/linux-2.6/xfs_aops.c | 2 +-
include/linux/backing-dev.h | 2 +
include/linux/writeback.h | 10 +--
include/trace/events/btrfs.h | 6 +-
include/trace/events/ext4.h | 6 +-
include/trace/events/writeback.h | 100 +++++++++++++++++-
mm/backing-dev.c | 21 +++-
mm/filemap.c | 6 +-
mm/page-writeback.c | 25 +++--
mm/rmap.c | 4 +-
15 files changed, 270 insertions(+), 159 deletions(-)

They are git pullable from

git://git.kernel.org/pub/scm/linux/kernel/git/wfg/writeback.git fs-writeback

Thanks to Jan and Dave for the careful reviews!

Thanks,
Fengguang


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/