From: Mingming Cao Subject: Re: [PATCH] EXT_MAX_BLOCK for >= 16TB fs Date: Tue, 08 Jul 2008 16:58:09 -0700 Message-ID: <1215561489.6820.20.camel@mingming-laptop> References: <1215449732.1167.11.camel@alpha.linsyssoft.com> <1215521471.3249.15.camel@alpha.linsyssoft.com> <1215523338.3249.18.camel@alpha.linsyssoft.com> <1215561399.6820.18.camel@mingming-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Ext4 Mailing List , adilger@Sun.COM, Theodore Tso To: Girish Shilamkar Return-path: Received: from e32.co.us.ibm.com ([32.97.110.150]:49257 "EHLO e32.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754829AbYGHX6N (ORCPT ); Tue, 8 Jul 2008 19:58:13 -0400 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e32.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id m68NqvjJ006261 for ; Tue, 8 Jul 2008 19:52:57 -0400 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m68NwCgt129442 for ; Tue, 8 Jul 2008 17:58:12 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m68NwAg6028021 for ; Tue, 8 Jul 2008 17:58:11 -0600 In-Reply-To: <1215561399.6820.18.camel@mingming-laptop> Sender: linux-ext4-owner@vger.kernel.org List-ID: oops, I saw your updated patch, thanks =E5=9C=A8 2008-07-08=E4=BA=8C=E7=9A=84 16:56 -0700=EF=BC=8CMingming Cao= =E5=86=99=E9=81=93=EF=BC=9A > Girish, thanks for sending out the patch. Looks like it's agains ext3= , > could you please port it to ext4? >=20 > Thanks, > Mingming > =E5=9C=A8 2008-07-08=E4=BA=8C=E7=9A=84 18:52 +0530=EF=BC=8CGirish Shi= lamkar=E5=86=99=E9=81=93=EF=BC=9A > > Oops ... > >=20 > > On Tue, 2008-07-08 at 18:21 +0530, Girish Shilamkar wrote: > > > Hi,=09 > > > Here is the patch for same. > > >=20 > > > Thanks, > > > Girish > > >=20 > > > On Mon, 2008-07-07 at 22:25 +0530, Girish Shilamkar wrote: > > > > Hi, > > > > The magic constant EXT_MAX_BLOCK =3D 0xffffffff in extents cod= e is used > > > > in some places to return "invalid block number", and to set the= extent > > > > length =3D "whole file" in other places. > > > > So with >=3D 16 TB fs we would prefer to use it differently. W= e can have > > > > EXT_UNSET_BLOCK =3D 1 to indicate "invalid block number" as it = will never > > > > be valid block for allocation. And for "whole file" usecase we = can > > > > continue using current EXT_MAX_BLOCK > > > >=20 > > > > Regards, > > > > Girish > > > >=20 > > > >=20 > > > >=20 > > > > -- > > > > To unsubscribe from this list: send the line "unsubscribe linux= -ext4" in > > > > the body of a message to majordomo@vger.kernel.org > > > > More majordomo info at http://vger.kernel.org/majordomo-info.h= tml > > >=20 > > > -- > > > To unsubscribe from this list: send the line "unsubscribe linux-e= xt4" in > > > the body of a message to majordomo@vger.kernel.org > > > More majordomo info at http://vger.kernel.org/majordomo-info.htm= l -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html