[blktests,v4,11/11] nvme{016,017}: Make the number iterations configurable
Commit Message
Some tests hard code high values of iterations. This makes them run
relatively long compared to the other tests. Introduce a new environment
variable nvme_num_iter to allow tune the runtime.
Reviewed-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Daniel Wagner <dwagner@suse.de>
---
Documentation/running-tests.md | 2 ++
tests/nvme/016 | 2 +-
tests/nvme/017 | 2 +-
tests/nvme/rc | 1 +
4 files changed, 5 insertions(+), 2 deletions(-)
@@ -107,6 +107,8 @@ The NVMe tests can be additionally parameterized via environment variables.
- nvme_img_size: '1G' (default)
Run the tests with given image size in bytes. 'm', 'M', 'g'
and 'G' postfix are supported.
+- nvme_num_iter: 1000 (default)
+ The number of iterations a test should do.
### Running nvme-rdma nvmeof-mp srp tests
@@ -17,7 +17,7 @@ test() {
echo "Running ${TEST_NAME}"
local port
- local iterations=1000
+ local iterations="${nvme_num_iter}"
local loop_dev
local subsys_nqn="blktests-subsystem-1"
@@ -18,7 +18,7 @@ test() {
local port
local file_path
- local iterations=1000
+ local iterations="${nvme_num_iter}"
local subsys_name="blktests-subsystem-1"
_setup_nvmet
@@ -18,6 +18,7 @@ def_hostnqn="$(cat /etc/nvme/hostnqn 2> /dev/null)"
def_hostid="$(cat /etc/nvme/hostid 2> /dev/null)"
nvme_trtype=${nvme_trtype:-"loop"}
nvme_img_size=${nvme_img_size:-"1G"}
+nvme_num_iter=${nvme_num_iter:-"1000"}
_nvme_requires() {
_have_program nvme