Valerie Henson writes:

[...]

 > 
 > You're right about needing to read the equivalent data-structure - for
 > other reasons, each continuation inode will need an easily accessible
 > list of byte ranges covered by that inode. (Sounds like, hey,
 > extents!) The important part is that you don't have go walk all the

I see. I was under impression that idea was to use indirect blocks
themselves as that data-structure, e.g., block number 0 to mark holes,
block number 1 to mark "block not in this continuation", and all other
block numbers for real blocks.

 > indirect blocks or check your bitmap.
 > 
 > -VAL

Nikita.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to