[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <1215540750.6011.10.camel@alpha.linsyssoft.com>
Date: Tue, 08 Jul 2008 23:42:30 +0530
From: Girish Shilamkar <Girish.Shilamkar@....COM>
To: Ext4 Mailing List <linux-ext4@...r.kernel.org>
Cc: adilger@....COM, Theodore Tso <tytso@....edu>
Subject: Re: [PATCH] EXT_MAX_BLOCK for >= 16TB fs
Hi,
Please disregard the last mail as it had incorrect patch, sorry for
that.
The correct patch is attached here.
Thanks,
Girish
On Tue, 2008-07-08 at 18:52 +0530, Girish Shilamkar wrote:
> Oops ...
>
> On Tue, 2008-07-08 at 18:21 +0530, Girish Shilamkar wrote:
> > Hi,
> > Here is the patch for same.
> >
> > Thanks,
> > Girish
> >
> > On Mon, 2008-07-07 at 22:25 +0530, Girish Shilamkar wrote:
> > > Hi,
> > > The magic constant EXT_MAX_BLOCK = 0xffffffff in extents code is used
> > > in some places to return "invalid block number", and to set the extent
> > > length = "whole file" in other places.
> > > So with >= 16 TB fs we would prefer to use it differently. We can have
> > > EXT_UNSET_BLOCK = 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
> > >
> > > Regards,
> > > Girish
> > >
> > >
> > >
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> > > the body of a message to majordomo@...r.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> > the body of a message to majordomo@...r.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
View attachment "change-EXT_MAX_BLOCK.patch" of type "text/x-patch" (3629 bytes)
Powered by blists - more mailing lists