Hi ,
I am testing mlx5 crypto driver/performance but the crypto device seems still disabled.
platform =>doca 1.5
test on dpdk-22.11 (test with only doca 1.5 also have the same problem)
root@localhost:/home/ubuntu/bf-build/dpdk/dpdk-22.11# env LD_LIBRARY_PATH=./build/drivers/ ./build/app/test/dpdk-test -c 1 -n 1 -a 03:00.0,class=crypto
EAL: Detected CPU lcores: 8
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode ‘PA’
EAL: VFIO support initialized
EAL: Probe PCI driver: mlx5_pci (15b3:a2d6) device: 0000:03:00.0 (socket -1)
mlx5_crypto: Not enough capabilities to support crypto operations, maybe old FW/OFED version?
mlx5_common: Failed to load driver crypto_mlx5
EAL: Requested device 0000:03:00.0 cannot be used
EAL: Bus (pci) probe failed.
APP: HPET is not enabled, using TSC as default timer
Thank you for posting your query on our community. I would like to confirm if you got an opportunity to review the following link which mentions the settings to be applied for crypto to take effect. Specifically "section 15.2 Configuration " —> https://doc.dpdk.org/guides/cryptodevs/mlx5.html
From the above mentioned section, it explains the following along with steps to be executed:
“When crypto engines are defined to work in wrapped import method, they come out of the factory in Commissioning mode, and thus, cannot be used for crypto operations yet. A dedicated tool is used for changing the mode from Commissioning to Operational”
Please ensure the settings are correctly set. If the issue still persists, I would like to request submitting a support ticket for further troubleshooting. The support ticket can be opened by emailing " Networking-support@nvidia.com "
Please note that an active support contract would be required for the same. For contracts information, please feel free to reach out to our contracts team at " Networking-Contracts@nvidia.com "