Prev: [PATCH 2/6] writeback: reduce calls to global_page_state in balance_dirty_pages()
Next: NFSv4: Add label recommended attribute and NFSv4 flags
From: Christoph Hellwig on 10 Jul 2010 22:50 On Sun, Jul 11, 2010 at 10:06:56AM +0800, Wu Fengguang wrote: > Andrew, > > Here are some writeback cleanups to avoid unnecessary calculation overheads, > and relative simple bug fixes. > > The patch applies to latest linux-next tree. The mmotm tree will need rebase > to include commit 32422c79 (writeback: Add tracing to balance_dirty_pages) > in order to avoid merge conflicts. Maybe it's a better idea to get them in through Jens' tree? At least he has handled all my flusher thread patches, and I have another big series in preparation which might cause some interesting conflicts if not merged through the same tree. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Wu Fengguang on 10 Jul 2010 23:20
[add cc to Jens] On Sun, Jul 11, 2010 at 10:44:04AM +0800, Christoph Hellwig wrote: > On Sun, Jul 11, 2010 at 10:06:56AM +0800, Wu Fengguang wrote: > > Andrew, > > > > Here are some writeback cleanups to avoid unnecessary calculation overheads, > > and relative simple bug fixes. > > > > The patch applies to latest linux-next tree. The mmotm tree will need rebase > > to include commit 32422c79 (writeback: Add tracing to balance_dirty_pages) > > in order to avoid merge conflicts. > > Maybe it's a better idea to get them in through Jens' tree? At least he > has handled all my flusher thread patches, and I have another big series > in preparation which might cause some interesting conflicts if not > merged through the same tree. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |