On Sun, Sep 30, 2012 at 05:28:23AM -0600, Alex Lyakas wrote: > Hi Josef, > I guess I am missing something, but I thought btrfs_next_leaf() should > just jump to the next leaf (or item, if it was added meanwhile) > irrespective of the key that is in the last slot of the current leaf. > The change you added is effective when there is a next leaf, but you > refuse to go there unless its first key has the same objectid. (I > think you use the ctree property that the key in the first node/leaf > of a tree block is equal to its parent's key). > Can you pls explain why you insist on the same objectid? >
It's to avoid another search forward. Unless I missed something everybody who calls btrfs_next_leaf() only wants to walk forward based on a particular item. If I've missed something and that's not the case then this needs to be dropped, or we can set some flag in path to ignore this logic, either way. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
