Yuriy Umanets 8ecf8dfcd7 bdev/crypto: Continue init after AESNI_MB failure ... - Continue init of the other crypto devices (mlx5) after failure of rte_vdev_init(AESNI_MB) in vbdev_crypto_init_crypto_drivers(). It simply may not be enabled in DPDK because it requires IPSec_MB>=1.0 installed in the system. Reproduces with --with-dpdk=dpdk/install option used, when the target DPDK is built without control of IPSec version from the SPDK side. - Updated crypto_ut to test the new behavior of error handling from rte_vdev_init(AESNI_MB) in vbdev_crypto_init_crypto_drivers(). Signed-off-by: Yuriy Umanets <yumanets@nvidia.com> Change-Id: Icd4db8877afe87db8166c40d6e7b414cd43c9c25 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11624 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: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>		2022-03-04 09:40:04 +00:00
..
crypto_ut.c	bdev/crypto: Continue init after AESNI_MB failure	2022-03-04 09:40:04 +00:00
Makefile	test/unit: remove duplicate mk/spdk.common.mk includes	2019-02-11 09:30:27 +00:00