The test case zbd/005 performs sequential writes to all sequential
write required zone on the test target zoned block device. To prepare
the device for this operation, the test invokes the blkzone reset
command. However, it takes very long time to complete.
The root cause of the long reset time is the offset option of the
blkzone reset command. This option specifies the first sequential write
required zone. When the offset options is provided, the kernel processes
the reset operation zone by zone. As a result, a separated zone reset
command is issued to each sequential write required zone, significantly
increasing the overall time.
To reduce the execution time of the blkzone reset command, remove the
offset option. Without this option, the kernel can perform a single zone
reset operation that resets all sequential write required zones.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@xxxxxxx>
---
tests/zbd/005 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/zbd/005 b/tests/zbd/005
index 4aa1ab5..790d24e 100755
--- a/tests/zbd/005
+++ b/tests/zbd/005
@@ -46,7 +46,7 @@ test_device() {
zbdmode=("--zonemode=zbd" "--max_open_zones=${moaz}")
fi
- blkzone reset -o "${ZONE_STARTS[zone_idx]}" "${TEST_DEV}"
+ blkzone reset "${TEST_DEV}"
_test_dev_set_scheduler deadline
--
2.50.1
