There is an existing unmap "workload" but it is not a
real workload - it's just used as a type of verify
function to check if an unmapped region later returns
zeroes. This has typically been true for Intel NVMe SSDs
but is not universal, so this functionality is not really
useful. It's not used anywhere in any of the tests in the
SPDK tree either.
So replace it with a real "unmap" workload that will
do sequential unmap operations on the underlying
bdev. A future enhancement could make these unmap
operations random across the bdev - but that can be
added later.
Signed-off-by: Jim Harris <james.r.harris@intel.com>
Change-Id: I99d7c2d455fb5c3c87712a5bbfd890d257630f88
Reviewed-on: https://review.gerrithub.io/413151
Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>
