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: <alpine.LFD.2.00.0904061255160.4134@localhost.localdomain>
Date:	Mon, 6 Apr 2009 12:57:09 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Theodore Tso <tytso@....edu>
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, 6 Apr 2009, Theodore Tso wrote:
> 
> 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?

Yes. I want to go back and see how much this all helps for the 
data=ordered case (if at all), but I think we should at least consider 
trying 'data=writeback' as a default.

Does the 'synchronize on rename / close-after-ftrucate' patches leave any 
other intersting cases open?

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