Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756835AbZDOUia (ORCPT ); Wed, 15 Apr 2009 16:38:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755357AbZDOUiV (ORCPT ); Wed, 15 Apr 2009 16:38:21 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:36487 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753878AbZDOUiU (ORCPT ); Wed, 15 Apr 2009 16:38:20 -0400 Date: Wed, 15 Apr 2009 13:35:23 -0700 (PDT) From: Linus Torvalds X-X-Sender: torvalds@localhost.localdomain To: Chris Mason cc: Jan Kara , "Theodore Ts'o" , Linux Kernel Developers List , Ext4 Developers List Subject: Re: [PATCH RFC] ext3 data=guarded v3 In-Reply-To: <1239816159-6868-1-git-send-email-chris.mason@oracle.com> Message-ID: References: <1239816159-6868-1-git-send-email-chris.mason@oracle.com> 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: 840 Lines: 22 On Wed, 15 Apr 2009, Chris Mason wrote: > > Here is another version of the data=guarded work for ext3. The main > difference between this code and yesterday's is the guarded writepage > function now sends any newly allocated block through the old data=ordered code. I'm inclined to apply the first two patches as infrastructure, since they seem to make sense regardless of data=ordered. The ability to get a callback when IO ends sounds like something that a number of cases might find intriguing, and it's obviously how the actual IO has worked internally anyway. Comments? 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/