linux-kernel - Re: [PATCH 0/8][RFC] IO latency/throughput fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090406183157.GD7376@mit.edu>
Date:	Mon, 6 Apr 2009 14:31:57 -0400
From:	Theodore Tso <tytso@....edu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Jens Axboe <jens.axboe@...cle.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/8][RFC] IO latency/throughput fixes

On Mon, Apr 06, 2009 at 08:45:09AM -0700, Linus Torvalds wrote:
> 
> With that request size limiting, my fsync pauses tend to be in the 250ms 
> range, with a one 0.75s outlier in the last few minutes. I can definitely 
> feel that quarter-second thing, and the .75s pause was a real stutter, but 
> boy what a difference. I don't get the uncontrollable urge to kill that 
> nasty background writer any more.

Cool!  Maybe we can make things even better, but given where we are
at, this brings up an question: given Jens block latency patches
(thanks, Jens!), and the patches which add the flush on
replace-via-rename/replace-via-truncate for ext3 data=writeback,
should we make ext3 data=writeback the default for 2.6.30?

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/