Fix for bad metadata capacity reported by dmesg

Metadata capacity reported by dmesg was actually a memory footprint.

A proper size of metadata is now reported.

Signed-off-by: Krzysztof Majzerowicz-Jaszcz <krzysztof.majzerowicz-jaszcz@intel.com>
This commit is contained in:
Krzysztof Majzerowicz-Jaszcz 2022-07-06 13:53:23 +02:00
parent 2defff1da0
commit e12803f547

View File

@ -800,8 +800,8 @@ finalize:
ocf_cache_log(cache, log_info, "Cache line size: %llu kiB\n", ocf_cache_log(cache, log_info, "Cache line size: %llu kiB\n",
line_size / KiB); line_size / KiB);
ocf_cache_log(cache, log_info, "Metadata capacity: %llu MiB\n", ocf_cache_log(cache, log_info, "Metadata size on device: %llu kiB\n",
(uint64_t)ocf_metadata_size_of(cache) / MiB); cache->device->metadata_offset / KiB);
result = ocf_metadata_concurrency_attached_init(&cache->metadata.lock, result = ocf_metadata_concurrency_attached_init(&cache->metadata.lock,
cache, ctrl->raw_desc[metadata_segment_hash].entries, cache, ctrl->raw_desc[metadata_segment_hash].entries,