Pass meta_sz through vos_pool_create call-stack
Issue
Project Management
Issue
Project Management
Description
Attachments
1
Activity
Show:
Tom Nabarro October 25, 2023 at 5:05 PM
PR landed to master in commit https://github.com/daos-stack/daos/commit/20404b20728b6c131a580b1fe16074a184a34f24
Tom Nabarro September 25, 2023 at 12:11 PM
is currently blocked on DAV allocator phase-II work by
Tom Nabarro September 22, 2023 at 1:30 PM
Tom Nabarro September 22, 2023 at 1:26 PM
trouble with PR when passing meta_sz to umem obj create:
engine log attached if you have any ideas or
Fixed
Details
Details
Assignee
Tom Nabarro
Tom NabarroReporter
Tom Nabarro
Tom NabarroPriority
P3-MediumAffects versions
Required for Version
Fix versions
Labels
Components
Story Points
5
Created September 22, 2023 at 1:21 PM
Updated October 10, 2024 at 1:42 PM
Resolved October 25, 2023 at 5:05 PM
Propagate meta-blob-size through pool create call-stack and use it (if set) in standard DAOS-pool case when creating meta-blob.
In order to maintain vos_pool_create behavior in other use cases (RDB/SysDB/tests) add meta_sz to vos_pool_create params so scm_sz == 0 can still be used to determine blob pre-allocation versus automatic creation.
In dmg, the meta size value is specified as the per-engine allocation whereas the value passed into vos_pool_create is the derived per-target value (which is distinct from the VOS-file size).