From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roman Zippel Subject: Re: [PATCH 2/9] sector_t format string Date: Thu, 10 Aug 2006 18:43:43 +0200 (CEST) Message-ID: References: <1155172843.3161.81.camel@localhost.localdomain> <20060809234019.c8a730e3.akpm@osdl.org> <44DB203A.6050901@garzik.org> <44DB25C1.1020807@garzik.org> <44DB27A3.1040606@garzik.org> <44DB3151.8050904@garzik.org> <17627.23974.848640.278643@stoffel.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Jeff Garzik , Andrew Morton , cmm@us.ibm.com, linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org Return-path: To: John Stoffel In-Reply-To: <17627.23974.848640.278643@stoffel.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi, On Thu, 10 Aug 2006, John Stoffel wrote: > The problem as I see it, is that you want extents, but you don't want > the RAM/DISK/ROM penalty of 64bit blocks, since embedded devices won't > ever go past the existing ext3 sizes, right? > > Is this a more clear statement of what you want? This is only about the runtime penalty. I'm less concerned about the disk structures, as soon as you use extents it's often more efficient than the current structure anyway. bye, Roman