On 11.04.2012 15:11, Jan Schmidt wrote: > Hi Jeff, > > On 05.04.2012 23:13, Jeff Mahoney wrote: >>> As a result, we must use a different addressing scheme. Extended >>> ref keys look like: >> >>> (inode objectid, BTRFS_INODE_EXTREF_KEY, hash) >> >>> Where hash is defined as a function of the parent objectid and link >>> name. >> >> I think this is effective. It will essentially have the same >> properties as a dirent but seeds the hash at objectid instead of ~1. > > The objectid is already part of the key. What's the point in seeding it > to crc32 instead of ~1? While reading the patch set, I'm just seeing that the first objectid is the inode's obectid while the latter is the parent's objectid. I'm fine with that. Thanks, -Jan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
