Spdk/test/nvmf
Konrad Sztyber e5f9e82291 bdev/nvme: add timeout option to start_discovery
It's now possible to specify a time to wait until a connection to the
discovery controller and the NVM controllers it exposes is made.

Whenever that time is exceeded, a callback is immediately executed.
However, depending on the stage of the discovery process, we might need
to wait a while before actually stopping it (e.g. because a controller
attach is in progress).  That means that a discovery service might be
visible for a while after it timed out.

Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com>
Change-Id: I2d01837b581e0fa24c8e777730d88d990c94b1d8
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12684
Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2022-05-18 07:24:06 +00:00
..
host bdev/nvme: add timeout option to start_discovery 2022-05-18 07:24:06 +00:00
target test/nvmf: reduce number of iterations in connect_disconnect test 2022-05-13 07:02:17 +00:00
common.sh test/vhost: Fix test exit when there are NICs without RDMA support 2022-05-09 09:35:42 +00:00
nvmf.sh test/nvmf: Multipath testing with ANA states support 2022-05-12 07:22:23 +00:00
README.md test: add parse_common_script_args function 2019-05-22 23:43:51 +00:00

NVMe-oF test scripts

The test scripts in this directory hierarchy can be run in isolation by passing the --iso flag when running the test script. This will set up the RDMA NIC for testing and then tear it back down again when the test is completed.