Re: writeback tree status (for 3.2 merge window)

[Christoph Hellwig]

On Tue, Nov 01, 2011 at 03:43:47PM +0800, Wu Fengguang wrote:
> Hi,
> 
> There are 3 patchsets sitting in the writeback tree.
> 
>         1) IO-less dirty throttling v12
>         https://github.com/fengguang/linux/commits/dirty-throttling-v12
> 
>         2) writeback reasons tracing from Curt Wohlgemuth
>         https://github.com/fengguang/linux/commits/writeback-reason
> 
>         3) writeback queuing changes from Jan Kara and me
>         https://github.com/fengguang/linux/commits/requeue-io-wait
> 
> They have been merged into this branch testing in linux-next for a while:
> 
> https://github.com/fengguang/linux/commits/writeback-for-next
> 
> Since (3) still has an unresolved issue (detailed in the below
> links), it looks better to hold it back for this merge window.

Given that we have run into issues so much with it that's proably
the better idea.

To fix the originally reported issue with the missing file size updates
in XFS we plan to simply log all filesize changes in XFS.  Currently I
had this in the 3.3 queue, but in the worst case we might have to move
this forward to 3.2.

> The patches from (1,2) together with 2 tracing patches essential for
> debugging (1) have been pushed to the "writeback-for-linus" branch:
> 
>         http://git.kernel.org/?p=linux/kernel/git/wfg/linux.git;a=shortlog;h=refs/heads/writeback-for-linus
> 
> If no objections, I'll send a pull request to Linus soon.

Please do so.  I'm really looking forward to see the I/O-less
balance_dirty_pages in ASAP.

--
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/