From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Tomas Subject: Re: [RFC 0/13] extents and 48bit ext3 Date: Fri, 09 Jun 2006 22:10:36 +0400 Message-ID: References: <1149816055.4066.60.camel@dyn9047017069.beaverton.ibm.com> <4488E1A4.20305@garzik.org> <20060609083523.GQ5964@schatzie.adilger.int> <44898EE3.6080903@garzik.org> <448992EB.5070405@garzik.org> <448997FA.50109@garzik.org> <44899A1C.7000207@garzik.org> <4489B83E.9090104@sbcglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Andrew Morton , Jeff Garzik , ext2-devel , linux-kernel@vger.kernel.org, Linus Torvalds , cmm@us.ibm.com, linux-fsdevel@vger.kernel.org, Alex Tomas , Andreas Dilger Return-path: To: artusemrys@sbcglobal.net In-Reply-To: <4489B83E.9090104@sbcglobal.net> (Matthew Frost's message of "Fri, 09 Jun 2006 13:04:46 -0500") 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 >>>>> Matthew Frost (MF) writes: MF> Alex Tomas wrote: >>>>>>> Jeff Garzik (JG) writes: JG> Think about how this will be deployed in production, long term. JG> If extents are not made default at some point, then no one will >> use JG> the feature, and it should not be merged. >> sorry, I disagree. for example, NUMA isn't default and shouldn't be. >> but we have it in the tree and any one may choose to use it. MF> NUMA is designed to cope with a hardware feature, which not everybody MF> has. Filesystem upgrades are not qualitatively similar; it does not MF> depend on one's hardware design as to whether one uses ext3, let alone MF> extents. Your logic is faulty. proposed 48bit extents patch addresses 2TB limit. thanks, Alex