[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1215561399.6820.18.camel@mingming-laptop>
Date: Tue, 08 Jul 2008 16:56:39 -0700
From: Mingming Cao <cmm@...ibm.com>
To: Girish Shilamkar <Girish.Shilamkar@....COM>
Cc: Ext4 Mailing List <linux-ext4@...r.kernel.org>, adilger@....COM,
Theodore Tso <tytso@....edu>
Subject: Re: [PATCH] EXT_MAX_BLOCK for >= 16TB fs
Girish, thanks for sending out the patch. Looks like it's agains ext3,
could you please port it to ext4?
Thanks,
Mingming
在 2008-07-08二的 18:52 +0530,Girish Shilamkar写道:
> 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
--
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
Powered by blists - more mailing lists