public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
* [RFC] EXT_MAX_BLOCK for >= 16TB fs
@ 2008-07-07 16:55 Girish Shilamkar
  2008-07-08 12:51 ` [PATCH] " Girish Shilamkar
  0 siblings, 1 reply; 6+ messages in thread
From: Girish Shilamkar @ 2008-07-07 16:55 UTC (permalink / raw)
  To: Ext4 Mailing List; +Cc: adilger, Theodore Tso

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




^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2008-07-08 23:58 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-07 16:55 [RFC] EXT_MAX_BLOCK for >= 16TB fs Girish Shilamkar
2008-07-08 12:51 ` [PATCH] " Girish Shilamkar
2008-07-08 13:22   ` Girish Shilamkar
2008-07-08 18:12     ` Girish Shilamkar
2008-07-08 23:56     ` Mingming Cao
2008-07-08 23:58       ` Mingming Cao

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox