I sent these questions to Matt Ahrens, but it occurred to me later that this might be a better place to ask. So far I have found very little information online. If anybody can answer these for me I would be very grateful.
1) What does the ddt_phys_type_t enum represent and what do the values mean? Specifically, what is the difference between DDT_PHYS_DITTO and the others? 2) What does the ddt_class_t enum represent and what do the values mean? Why do we keep different dedup objects on disk and in-core for each class in this enum? This seems related to question 1. 3) It looks to me that each ddt_phys_t can support up to SPA_DVAS_PER_BP (3) DVAs and each ddt_entry_t can support up to DDT_PHYS_TYPES (4). Does that mean that the dedup table can store up to 12 copies of each dedup'd block? That seems a bit excessive. Thanks, Tom Caputi ------------------------------------------- openzfs-developer Archives: https://www.listbox.com/member/archive/274414/=now RSS Feed: https://www.listbox.com/member/archive/rss/274414/28015062-cce53afa Modify Your Subscription: https://www.listbox.com/member/?member_id=28015062&id_secret=28015062-f966d51c Powered by Listbox: http://www.listbox.com
