From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [GIT PULL] block/io bits for 2.6.35-rc
Date: Thu, 10 Jun 2010 18:40:48 +0200 [thread overview]
Message-ID: <20100610164048.GA25171@lst.de> (raw)
In-Reply-To: <4C1111ED.6020008@fusionio.com>
On Thu, Jun 10, 2010 at 06:25:17PM +0200, Jens Axboe wrote:
> I agree, it's late and it makes me nervous too. I had them cook for
> a day, didn't see any problems. And Christoph would not send it in
> unless it passes at least xfs qa, which is what found the problems
> last time (the ones we reverted).
>
> It's fixing a regression where umount takes a LONG time if you have
> a lot of dirty inodes, since it basically degenerates to a data
> integrity writeback instead of a simple WB_SYNC_NONE. If it wasn't
> fixing a nasty regression (the distros are all wanting a real fix
> for this, it's a user problem), I would not be submitting this code
> at this point in time.
Maybe give it a bit more beating in linux-next and send it off to Linus
once he's back from his vacation?
next prev parent reply other threads:[~2010-06-10 16:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 13:44 [GIT PULL] block/io bits for 2.6.35-rc Jens Axboe
2010-06-10 15:55 ` Linus Torvalds
2010-06-10 16:25 ` Jens Axboe
2010-06-10 16:40 ` Christoph Hellwig [this message]
2010-06-10 16:59 ` Jens Axboe
2010-06-10 17:03 ` Linus Torvalds
2010-06-10 16:44 ` Brian Bloniarz
2010-06-27 23:10 ` Mark Lord
2010-06-28 7:03 ` Jens Axboe
2010-06-28 9:41 ` Christoph Hellwig
2010-06-28 13:51 ` Mark Lord
2010-06-28 14:05 ` Brian Bloniarz
2010-06-28 14:33 ` Mark Lord
2010-06-28 17:32 ` Jens Axboe
2010-06-28 20:55 ` Mark Lord
2010-06-10 16:55 ` Linus Torvalds
2010-06-10 17:00 ` Jens Axboe
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=20100610164048.GA25171@lst.de \
--to=hch@lst.de \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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