( Sorry for top-posting. ) I have this patchset v4 since 24-May in my series. Is this going to be accepted within merge-window for 2.6.40 (or 3.0)? - Sedat - On Tue, May 24, 2011 at 7:14 AM, Wu Fengguang <fengguang.wu@xxxxxxxxx> wrote: > > Andrew, > > The first 10 patches are already in -mm tree, with updates: > > - remove "writeback: pass writeback_control down to move_expired_inodes()", and > Âresolve the resulting merge conflicts in other patches. > - move ahead the sync livelock prevention patches (01, 02) so that (04) won't livelock sync > - merge the three -mm fixes to (08) > - fixed changelog of (01) > - rename .for_sync to .tagged_writepages > >    Â[PATCH 01/18] writeback: introduce .tagged_writepages for the WB_SYNC_NONE sync stage >    Â[PATCH 02/18] writeback: update dirtied_when for synced inode to prevent livelock >    Â[PATCH 03/18] writeback: introduce writeback_control.inodes_cleaned >    Â[PATCH 04/18] writeback: try more writeback as long as something was written >    Â[PATCH 05/18] writeback: the kupdate expire timestamp should be a moving target >    Â[PATCH 06/18] writeback: sync expired inodes first in background writeback >    Â[PATCH 07/18] writeback: refill b_io iff empty >    Â[PATCH 08/18] writeback: split inode_wb_list_lock into bdi_writeback.list_lock >    Â[PATCH 09/18] writeback: elevate queue_io() into wb_writeback() >    Â[PATCH 10/18] writeback: avoid extra sync work at enqueue time > > The following 6 patches are trivial and safe > >    Â[PATCH 11/18] writeback: add bdi_dirty_limit() kernel-doc >    Â[PATCH 12/18] writeback: skip balance_dirty_pages() for in-memory fs >    Â[PATCH 13/18] writeback: remove writeback_control.more_io >    Â[PATCH 14/18] writeback: remove .nonblocking and .encountered_congestion >    Â[PATCH 15/18] writeback: trace event writeback_single_inode >    Â[PATCH 16/18] writeback: trace event writeback_queue_io > > Patch 17 is a bit more complex > >    Â[PATCH 17/18] writeback: make writeback_control.nr_to_write straight >    Â[PATCH 18/18] writeback: rearrange the wb_writeback() loop > > Thanks to Jan and Dave for the careful reviews! > > The patches are git pullable from > > git://git.kernel.org/pub/scm/linux/kernel/git/wfg/writeback.git fs-writeback > > Âfs/block_dev.c          |  16 +- > Âfs/btrfs/extent_io.c       |  Â2 - > Âfs/ext4/inode.c         Â|  Â4 +- > Âfs/fs-writeback.c        Â| Â411 +++++++++++++++++++++----------------- > Â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    Â|  14 +- > Âinclude/trace/events/btrfs.h   |  Â6 +- > Âinclude/trace/events/ext4.h   Â|  Â6 +- > Âinclude/trace/events/writeback.h | Â137 ++++++++++++-- > Âmm/backing-dev.c         |  30 ++- > Âmm/filemap.c           |  Â6 +- > Âmm/page-writeback.c       Â|  42 ++-- > Âmm/rmap.c            Â|  Â4 +- > Â16 files changed, 420 insertions(+), 270 deletions(-) > > Thanks, > Fengguang > > -- > 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 > -- 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
