From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [RFC 0/13] extents and 48bit ext3 Date: Sat, 10 Jun 2006 11:03:14 -0400 Message-ID: <448ADF32.3070705@garzik.org> References: <20060610134645.GB11634@stusta.de> <20060610144228.GA6416@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Andrew Morton , ext2-devel , linux-kernel@vger.kernel.org, Adrian Bunk , Linus Torvalds , Gerrit Huizenga , cmm@us.ibm.com, linux-fsdevel@vger.kernel.org, Alex Tomas , Andreas Dilger Return-path: To: Ingo Molnar In-Reply-To: <20060610144228.GA6416@elte.hu> 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 Ingo Molnar wrote: > the ext3 -> ext4 patches add +2115 lines of code (which 2115 lines solve > the biggest performance and scaling problem ext3 currently has), which > is 1.9% of the linecount of XFS. Indeed! > ext3 does quite a few things to stay compatible with ext2 - and frankly, > i very much expected it to do that when i migrated my ext2 data to ext3. > The days of "change the world in an incompatible way and dont look back" > are gone. I agree with your point in the thread -- most users and distros don't change their main fs on a whim. But I also point out that these extent+48bit changes _do_ change the format in an incompatible way... Jeff