20f4a21d84
nvme-cli in NVMf tests currently fails to initialize the NVMe driver and exits straight away [1]. It expects the primary process to initialize the driver first, but since the primary process doesn't operate on any NVMe devices, it doesn't initialize the driver at all. Fix this by running nvme-cli without multi-process mode. In NVMf tests, nvme-cli is only used to discover, connect and disconnect from an SPDK NVMf target. It does not need to access any shared memory resources. This wasn't an issue before, because we used an outdated DPDK version for nvme-cli which didn't detect any other shared memory processes of SPDK. [1] nvme.c: 337:nvme_driver_init: *ERROR*: primary process is not started yet Change-Id: Id56f94c6655049e87ab9d93ee38853faf40a11e5 Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442552 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> |
||
|---|---|---|
| .. | ||
| aer | ||
| deallocated_value | ||
| e2edp | ||
| err_injection | ||
| overhead | ||
| reset | ||
| sgl | ||
| hotplug.sh | ||
| Makefile | ||
| nvme.sh | ||
| spdk_nvme_cli.sh | ||