> As to the differences to idr: > - as David pointed out, idr works on int, while I always need u64 to > represent btrfs logical addresses. > - as I understand idr (though I never used it), it is designed to manage > small consecutive integers, while ulists hold completely unrelated > numbers, e.g. btrfs logical adresses. For small sets ulists might be > much faster than idr > - ulists as used here are very short lived. I don't know if idr handles > this case well > - the purpose of ulists is to add a specific number, and not to find a > free one. I don't see a direct interface for this in idr. Okay. Fair enough. I would suggest to put it into lib/* and submit it to the mainline kernel and see what happens. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- 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
