Bugzilla – Bug 1221262
Regarding version-matching between kernel module mlx5_core and Mellanox ConnectX NIC firmware
Last modified: 2024-05-13 05:28:50 UTC
Hi guys, In our ObjectStorage products, we run NVMe_over_RDMA and NVMe_over_TCP traffic through Mellanox ConnectX NICs. You know Mellanox has a series of ConnectX NIC models. E.g., ConnectX-4 Lx, ConnectX-6 Dx, etc. And for each NIC model, there is a series of firmware versions. E.g., for ConnectX-4 Lx, the available firmware versions include 14.27.1016, 14.28.2006, etc. On the other hand, in SLES 15 SP4, the kernel module mlx5_core is the driver of the ConnectX NICs. As an alternative, the MLNX_OFED also provides its own implementation of the kernel module mlx5_core. For us, in some products, we use the MLNX_OFED, in some products, we use the SLES 15 SP4 inbox drivers. However, as I know, in each release of the MLNX_OFED, for each ConnectX NIC model, they always announce an explicit list of supported firmware versions. E.g., in MLNX_OFED 4.9-6.0.6.0-LTS, for ConnectX-4 Lx, the supported firmware versions are 14.27.1016, 14.28.2006. Ref:https://docs.nvidia.com/networking/display/mlnxofedv496060lts/general+support+in+mlnx_ofed So our question is, in case we use SLES 15 SP4 inbox drivers instead of the drivers from the MLNX_OFED, are there any similar version-matching requirements between kernel module mlx5_core and Mellanox ConnectX NIC firmware. If so, for RDMA and TCP/IP, do the version-matching requirements only apply to one of them or both?
Any response?
> in case we use SLES 15 SP4 inbox drivers instead of the drivers from the > MLNX_OFED, are there any similar version-matching requirements between > kernel module mlx5_core and Mellanox ConnectX NIC firmware. As far I can tell, the similar dependency between driver and firmware. Though I can't don't know the details. @Thomas, do you happen to know more about this?
@Daniel Wagner Thanks for the brief answer. Could anyone provide us with an explicit and detailed answer?
Any update?