The test verifies that bdev-based QoS settings are correctly applied on NVMe/TCP devices. Other device types supporting bdev-based QoS will share most of the code, so NVMe/TCP is a good test vehicle, as it's the easiest one to set up. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Ic715483e888a7219fd27367d527201d75e8b69a2 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14270 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
15 lines
462 B
Bash
Executable File
15 lines
462 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
testdir=$(readlink -f "$(dirname "$0")")
|
|
rootdir=$(readlink -f "$testdir/../..")
|
|
|
|
source "$rootdir/test/common/autotest_common.sh"
|
|
|
|
run_test "sma_nvmf_tcp" $testdir/nvmf_tcp.sh
|
|
run_test "sma_vfiouser_qemu" $testdir/vfiouser_qemu.sh
|
|
run_test "sma_plugins" $testdir/plugins.sh
|
|
run_test "sma_discovery" $testdir/discovery.sh
|
|
run_test "sma_vhost" $testdir/vhost_blk.sh
|
|
run_test "sma_crypto" $testdir/crypto.sh
|
|
run_test "sma_qos" $testdir/qos.sh
|