ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
cddfe002e1
Spdk/test/nvmf/target/bdevio.sh

38 lines
1.1 KiB
Bash
Raw Normal View History

test/nvmf: add bdevio test This tests a variety of bdev-related commands against our NVMe-oF target. The key ones are write_zeroes and nvme_passthrough which until now weren't being tested at all. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Id8a5cfb2e41c2a7e8fd940b61b43a80c39993f9a Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/452936 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com>
2019-05-02 23:55:49 +00:00
#!/usr/bin/env bash
testdir=$(readlink -f $(dirname $0))
rootdir=$(readlink -f $testdir/../../..)
source $rootdir/test/common/autotest_common.sh
source $rootdir/test/nvmf/common.sh
MALLOC_BDEV_SIZE=64
MALLOC_BLOCK_SIZE=512
rpc_py="$rootdir/scripts/rpc.py"
set -e
test/nvmf: reduce duplication between target scripts All of the checking for NVMF_FIRST_TARGET_IP, starting the target, waiting on the target and modprobing nvme-rdma is duplicated in every script. So move a lot of this either to nvmftestinit() or a new nvmfappstart() function in common.sh. Also just kill the nvmf target in nvmftestfini, rather than the script to explicitly kill it. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I5864404610a4244473f460d48264de92687ed867 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454678 Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-05-13 19:11:00 +00:00
timing_enter bdevio
test/nvmf: simplify "iso" parameter Pull this parameter when sourcing common.sh and set a RUN_IN_ISOLATION flag if it was specified. This reduces the overall code a bit plus avoids having to pass the "iso" parameter to nvmftestinit and nvmftestfini. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Idbbe27bfb7b62857500176cdb5d90e381fce4ffc Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454814 Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-05-16 19:38:53 +00:00
nvmftestinit
test/nvmf: reduce duplication between target scripts All of the checking for NVMF_FIRST_TARGET_IP, starting the target, waiting on the target and modprobing nvme-rdma is duplicated in every script. So move a lot of this either to nvmftestinit() or a new nvmfappstart() function in common.sh. Also just kill the nvmf target in nvmftestfini, rather than the script to explicitly kill it. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I5864404610a4244473f460d48264de92687ed867 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454678 Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-05-13 19:11:00 +00:00
nvmfappstart "-m 0xF"
test/nvmf: add bdevio test This tests a variety of bdev-related commands against our NVMe-oF target. The key ones are write_zeroes and nvme_passthrough which until now weren't being tested at all. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Id8a5cfb2e41c2a7e8fd940b61b43a80c39993f9a Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/452936 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com>
2019-05-02 23:55:49 +00:00
test/nvmf: remove -p num_queues restrictions There's a bug in Linux 5.1 (possibly 5.0 too) where the kernel initiator driver crashes if it can't get one queue per CPU. This will get fixed eventually, but for now we need to remove the cases where we restrict the number of queues per controller so that we can test on newer kernels. Even on cases where we're testing the SPDK initiator, there's no real need to restrict the number of queue pairs. The kernel will eventually get fixed, but we should be testing with default behavior anyways (the kernel wants lots of queues). We'll also want to add some regression tests to make sure the kernel doesn't break again. But that will all come later. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I9979e6d94456e075688b822b042936b63e518a4a Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454819 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2019-05-16 21:39:52 +00:00
$rpc_py nvmf_create_transport -t rdma -u 8192
test/nvmf: add bdevio test This tests a variety of bdev-related commands against our NVMe-oF target. The key ones are write_zeroes and nvme_passthrough which until now weren't being tested at all. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Id8a5cfb2e41c2a7e8fd940b61b43a80c39993f9a Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/452936 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com>
2019-05-02 23:55:49 +00:00
$rpc_py construct_malloc_bdev $MALLOC_BDEV_SIZE $MALLOC_BLOCK_SIZE -b Malloc0
$rpc_py nvmf_subsystem_create nqn.2016-06.io.spdk:cnode1 -a -s SPDK00000000000001
$rpc_py nvmf_subsystem_add_ns nqn.2016-06.io.spdk:cnode1 Malloc0
test/nvmf: use NVMF_PORT consistently A lot of places were still hardcoding 4420 directly. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Iff8a549addeb05e441fe3b035a84a0f8a6bf2205 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/456666 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2019-06-03 16:15:25 +00:00
$rpc_py nvmf_subsystem_add_listener nqn.2016-06.io.spdk:cnode1 -t rdma -a $NVMF_FIRST_TARGET_IP -s $NVMF_PORT
test/nvmf: add bdevio test This tests a variety of bdev-related commands against our NVMe-oF target. The key ones are write_zeroes and nvme_passthrough which until now weren't being tested at all. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Id8a5cfb2e41c2a7e8fd940b61b43a80c39993f9a Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/452936 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com>
2019-05-02 23:55:49 +00:00
echo "[Nvme]" > $testdir/bdevperf.conf
test/nvmf: use NVMF_PORT consistently A lot of places were still hardcoding 4420 directly. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Iff8a549addeb05e441fe3b035a84a0f8a6bf2205 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/456666 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2019-06-03 16:15:25 +00:00
echo " TransportID \"trtype:rdma adrfam:IPv4 subnqn:nqn.2016-06.io.spdk:cnode1 traddr:$NVMF_FIRST_TARGET_IP trsvcid:$NVMF_PORT\" Nvme0" >> $testdir/bdevperf.conf
test/nvmf: add bdevio test This tests a variety of bdev-related commands against our NVMe-oF target. The key ones are write_zeroes and nvme_passthrough which until now weren't being tested at all. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Id8a5cfb2e41c2a7e8fd940b61b43a80c39993f9a Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/452936 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com>
2019-05-02 23:55:49 +00:00
$rootdir/test/bdev/bdevio/bdevio -c $testdir/bdevperf.conf
rm -rf $testdir/bdevperf.conf
$rpc_py delete_nvmf_subsystem nqn.2016-06.io.spdk:cnode1
trap - SIGINT SIGTERM EXIT
nvmfcleanup
test/nvmf: simplify "iso" parameter Pull this parameter when sourcing common.sh and set a RUN_IN_ISOLATION flag if it was specified. This reduces the overall code a bit plus avoids having to pass the "iso" parameter to nvmftestinit and nvmftestfini. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Idbbe27bfb7b62857500176cdb5d90e381fce4ffc Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454814 Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-05-16 19:38:53 +00:00
nvmftestfini
test/nvmf: add bdevio test This tests a variety of bdev-related commands against our NVMe-oF target. The key ones are write_zeroes and nvme_passthrough which until now weren't being tested at all. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Id8a5cfb2e41c2a7e8fd940b61b43a80c39993f9a Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/452936 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com>
2019-05-02 23:55:49 +00:00
timing_exit bdev_io_wait
Reference in New Issue Copy Permalink