Re: [dm-devel] Why does dm-thin pool metadata space map use 4K page to carry index ?

2019-09-05 Thread jianchao wang
Hi Joe Thanks for your kindly response On Thu, Sep 5, 2019 at 6:38 PM Joe Thornber wrote: > On Thu, Sep 05, 2019 at 02:43:28PM +0800, jianchao wang wrote: > > But why does it use this 4K page instead of btree as the disk sm ? > > > > The brb mechanism seem be able to avoid the nested block

Re: [dm-devel] Why does dm-thin pool metadata space map use 4K page to carry index ?

2019-09-05 Thread Joe Thornber
On Thu, Sep 05, 2019 at 02:43:28PM +0800, jianchao wang wrote: > But why does it use this 4K page instead of btree as the disk sm ? > > The brb mechanism seem be able to avoid the nested block allocation > when do COW on the metadata sm btree. > > Would anyone please help to tell why does it use

[dm-devel] Why does dm-thin pool metadata space map use 4K page to carry index ?

2019-09-05 Thread jianchao wang
Hi As the code, The metadata space map use following structure which locates on a 4K page on disk to carry the disk_index_entry. The on-disk format of metadata spacemap The metadata space's bitmap root is a #define MAX_METADATA_BITMAPS 255 struct disk_metadata_index { __le32 csum;