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 15:27:32 +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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Andrew Morton , linux-fsdevel@vger.kernel.org, ext2-devel@lists.sourceforge.net, cmm@us.ibm.com, linux-kernel@vger.kernel.org Return-path: To: Jeff Garzik In-Reply-To: <44DB3151.8050904@garzik.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ext2-devel-bounces@lists.sourceforge.net Errors-To: ext2-devel-bounces@lists.sourceforge.net List-Id: linux-fsdevel.vger.kernel.org Hi, On Thu, 10 Aug 2006, Jeff Garzik wrote: > > Considering the amount of complexity we add for the high end, why is it > > suddenly a bad thing to add even a _little_ complexity for the other end? > > This is ext4 not ext3 we're talking about. The next gen Linux filesystem > should be tuned for modern machines -- 64bit, moving forward -- while still > working just fine on 32bit. If you force everyone to use 64bit sector numbers, I don't understand how you can claim "still working just fine on 32bit"? At some point ext4 is probably going to be the de facto standard, which very many people want to use, because it has all the new features, which won't be ported to ext2/3. So I still don't understand, what's so wrong about a little tuning in both directions? bye, Roman ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642