From 99550a756d38c33c730d7b2c3a93d1287869b47c Mon Sep 17 00:00:00 2001 From: Niklas Cassel Date: Tue, 18 May 2021 07:35:01 +0000 Subject: [PATCH] bdev/fio_plugin: fix typo in README.md The definition is that: max active zones >= max open zones. The REAME.md incorrectly writes max active twice. Fix this typo in the README.md. Signed-off-by: Niklas Cassel Change-Id: I4b7d24d7bd1efcbe1608d3ee04d8900f83857f5e Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/7912 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins Reviewed-by: Aleksey Marchuk Reviewed-by: Ziye Yang Reviewed-by: Tomasz Zawadzki --- examples/bdev/fio_plugin/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/bdev/fio_plugin/README.md b/examples/bdev/fio_plugin/README.md index 7794cd539..aaa65e64e 100644 --- a/examples/bdev/fio_plugin/README.md +++ b/examples/bdev/fio_plugin/README.md @@ -103,7 +103,7 @@ Zoned block devices may also have a resource constraint on the number of zones t any point in time. Unlike ``max_open_zones``, fio currently does not manage this constraint, and there is thus no option to limit it either. -Since the max active zones limit (by definition) has to be greater than or equal to the max active +Since the max active zones limit (by definition) has to be greater than or equal to the max open zones limit, the easiest way to work around that fio does not manage this constraint, is to start with a clean state each run (except for read-only workloads), by resetting all zones before fio starts running its jobs by using the engine option: