From: Christoph Hellwig <hch@infradead.org>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>, Jan Kara <jack@suse.cz>,
Curt Wohlgemuth <curtw@google.com>,
Michael Rubin <mrubin@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
Dave Chinner <david@fromorbit.com>,
Greg Thelen <gthelen@google.com>,
Minchan Kim <minchan.kim@gmail.com>,
Vivek Goyal <vgoyal@redhat.com>,
Andrea Righi <arighi@develer.com>, linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Tang Feng <feng.tang@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
xfs@oss.sgi.com
Subject: Re: writeback tree status (for 3.2 merge window)
Date: Wed, 2 Nov 2011 05:10:12 -0400 [thread overview]
Message-ID: <20111102091012.GA25879@infradead.org> (raw)
In-Reply-To: <20111101074347.GA23644@localhost>
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.
next prev parent reply other threads:[~2011-11-02 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 7:43 writeback tree status (for 3.2 merge window) Wu Fengguang
2011-11-02 9:10 ` Christoph Hellwig [this message]
2011-11-02 15:13 ` Wu Fengguang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111102091012.GA25879@infradead.org \
--to=hch@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arighi@develer.com \
--cc=curtw@google.com \
--cc=david@fromorbit.com \
--cc=feng.tang@intel.com \
--cc=fengguang.wu@intel.com \
--cc=gthelen@google.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=mrubin@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@redhat.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).