Closed jaehshim closed 4 years ago
Location (Korea, USA, China, India, etc.) Korea
Describe the bug In running sample_test_async, KVSSD's capacity is printed well. However, KVSSD's utilization is always printed as 0.
To Reproduce Steps to reproduce the behavior:
Expected behavior The total size written is 512GB so in sample_code_async, KVSSD's utilization should be printed as 143.
Screenshots
System environment (please complete the following information)
Workload
Additional context Add any other context about the problem here.
The implementation of the utilization in the firmware and KV API. Please use the latest firmware to test (ETA51KBV).
It worked with the latest firmware.
Thanks
Location (Korea, USA, China, India, etc.) Korea
Describe the bug In running sample_test_async, KVSSD's capacity is printed well. However, KVSSD's utilization is always printed as 0.
To Reproduce Steps to reproduce the behavior:
Expected behavior The total size written is 512GB so in sample_code_async, KVSSD's utilization should be printed as 143.
Screenshots
System environment (please complete the following information)
Workload
Additional context Add any other context about the problem here.