Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932785AbXASAS4 (ORCPT ); Thu, 18 Jan 2007 19:18:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932787AbXASAS4 (ORCPT ); Thu, 18 Jan 2007 19:18:56 -0500 Received: from smtp.osdl.org ([65.172.181.24]:55481 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932785AbXASASz (ORCPT ); Thu, 18 Jan 2007 19:18:55 -0500 Date: Thu, 18 Jan 2007 16:17:41 -0800 From: Andrew Morton To: Grzegorz Kulewski Cc: hch@infradead.org, aia21@cam.ac.uk, torvalds@osdl.org, linux-kernel@vger.kernel.org, linux-ntfs-dev@lists.sourceforge.net Subject: Re: NTFS Message-Id: <20070118161741.6ac4e423.akpm@osdl.org> In-Reply-To: References: <1169115951.5408.10.camel@imp.csi.cam.ac.uk> <20070118222243.GA14047@infradead.org> <20070118143506.4d007aad.akpm@osdl.org> <20070118223813.GA6589@infradead.org> <20070118145439.b8d84d6b.akpm@osdl.org> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.19; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1464 Lines: 31 > On Fri, 19 Jan 2007 00:27:17 +0100 (CET) Grzegorz Kulewski wrote: > On Thu, 18 Jan 2007, Andrew Morton wrote: > >> On Thu, 18 Jan 2007 22:38:13 +0000 Christoph Hellwig wrote: > >> On Thu, Jan 18, 2007 at 02:35:06PM -0800, Andrew Morton wrote: > >>>> Cool. That means ->put_inode is gone in -mm. Andrew, what are the > >>>> plans for sending the patches to make the ext2 preallocation work > >>>> like ext3 to Linus? > >>> > >>> Cautious. I'm not sure that we ever want to merge them, really - ext2 is > >>> more a reference filesystem than a real one nowadays, and making it more > >>> complex detracts from that. > >> > >> The again while the old preallocation code might be simpler it's also utterly > >> braindead and we need to make sure no one is going to copy this :) > > > > Good point ;) > > Are you refering to that particular implementation in ext2 or to the > whole method od doing it implemented currently in ext2? It's a patch which cross-ports ext3's block-reservation code into ext2. > When can I read about it (description of the new method/implementation in > ext3 and why is it better) some more? Hard. google(ext3 reservations) is a starting point. - 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/