+5
−2
Loading
Some nvmf tests requires either kernel initiator (nvme connect, nvme discover) or the kernel target (nvmet config) in order to run. It might not be possible or desired to run them in some environments, mainly containerized: - container would need to be run with proper host path mounts and eaither --privileged flag (in case of Docker) or some more fine-graned set of capabilities. - running multiple containers in parallel accessing same kernel nvmf interfaces would interfere SPDK_TEST_SKIP_NVMF_KERNEL_TESTS has to be explicitly enabled in order to skip such test scope. There is no change in the existing behavior when flag is not set. Change-Id: Id18017cf8edbe6e3738d25d85b1533ee325be4b4 Signed-off-by:Krzysztof Goreczny <krzysztof.goreczny@dell.com> Reviewed-on: https://review.spdk.io/c/spdk/spdk/+/26331 Reviewed-by:
Michal Berger <michal.berger@nutanix.com> Reviewed-by:
Boris Glimcher <Boris.Glimcher@emc.com> Tested-by:
SPDK Automated Test System <spdkbot@gmail.com> Reviewed-by:
Konrad Sztyber <ksztyber@nvidia.com> Reviewed-by:
Jim Harris <jim.harris@nvidia.com>