Fix some scaling problems for large VGs (many LVs)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 of 5 patches 0 repliesNew
1 of 5 patches is in this archive. The cover letter announces 5.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 2/5 | Remove vg_validate call when parsing cached metadata. | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] Fix some scaling problems for large VGs (many LVs)
..
Quoted 8 lines
Milan Broz (5):
Use hash table for quick lv reference when reading metadata. Removevg_validatecall when parsing cached metadata. Optimise PV segments search.
Do not traverse PV segment list twice.
Fix all segments memory is allocated from vg private mempool.
Quoted 12 lines
lib/cache/lvmcache.c | 3 +- lib/format_text/import.c | 2 +- lib/format_text/import_vsn1.c | 42 +++++++++++++++++++++------- lib/metadata/lv_manip.c | 2 +- lib/metadata/merge.c | 4 +- lib/metadata/metadata.c | 12 -------- lib/metadata/metadata.h | 3 -- lib/metadata/pv_alloc.h | 4 ++- lib/metadata/pv_manip.c | 60 ++++++++++++++++++++++++++++------------ 9 files changed, 81 insertions(+), 51 deletions(-)
Patch set goes to right direction - but still there is probably more complex solution - In activation we could keep locked & parsed VG data in volume_group structure in memory - instead of parsing them for each LV again. (for the case of having like 3000LV in one VG)
Zdenek