Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757417AbZDFT7J (ORCPT ); Mon, 6 Apr 2009 15:59:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752249AbZDFT6y (ORCPT ); Mon, 6 Apr 2009 15:58:54 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:43348 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751804AbZDFT6y (ORCPT ); Mon, 6 Apr 2009 15:58:54 -0400 Date: Mon, 6 Apr 2009 12:57:09 -0700 (PDT) From: Linus Torvalds X-X-Sender: torvalds@localhost.localdomain To: Theodore Tso cc: Jens Axboe , Linux Kernel Mailing List Subject: Re: [PATCH 0/8][RFC] IO latency/throughput fixes In-Reply-To: <20090406183157.GD7376@mit.edu> Message-ID: References: <1239022088-29002-1-git-send-email-jens.axboe@oracle.com> <20090406151054.GD5178@kernel.dk> <20090406183157.GD7376@mit.edu> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 903 Lines: 23 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/