nvmf_vhost test verifies multiple components at once. In this case the number of NVMe-oF I/O qpairs per controller is limited to just 4. When a VM connected to the vhost_tgt is booted, the vhost controller is started/destroyed multiple times. The quick succession of getting I/O channels and asynchronous nature of NVMe-oF qpair deletion/creation, results in exhausting the free qpair ids. There is no reason to limit the number of NVMe-oF I/O qpairs in this test. If there ever is a need, a new test could be added exploring behaviour of components (like vhost) when get I/O channel fails. Fixes #2517 Change-Id: I32455c0499a1b79c82f921aaac193a83bd9cb468 Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14626 Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
---|---|---|
.. | ||
host | ||
target | ||
common.sh | ||
nvmf.sh | ||
README.md |
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.