Upgrade recommendations
Upgrade the driver,as a best practice.
Problems Solved
New Functions
Upgrade recommendations
Upgrade the driver,as a best practice.
Problems Solved
New Functions
Upgrade recommendations
Upgrade the driver,as a best practice.
Problems Solved
New Functions
Upgrade recommendations
Upgrade the driver,as a best practice.
Problems Solved
1.Fixed the setting of ATS for DMABUF MRs that caused some MRs to miss the ATS enablement. Lack of ATS enablement on DMABUF MRs results in slower performance when using these MRs.
2.On rare occasions, rdmacm applications could not find the device upon creating new RDMA devices, as the CMA driver lost some of the devices due to an overflow issue.
3.Fixed an issue that could have caused memory corruption when running XDP traffic.
4.Fixed an issue that prevented the tc_wrap tool from properly working when VLAN is configured as the tool wrongly handled the library function return value.
5.Fixed an issue that caused a deadlock in the flow of disabling the LAG when changing eswitch mode from switchdev to legacy when a LAG bond existed on the machine.
6.Fixed an issue related to the driver's internal MR cache cleanup that caused high memory consumption on the host.
New Functions
1.Added support for the following OSes:RHEL 8.10、RHEL 9.4、Debian 12.5
Version:23.10-1.1.9.0(2024/1/5)
Upgrade recommendations
Upgrade the driver,as a best practice.
Problems Solved
1.Resolved an issue on ConnectX-4 Lx, where the VF state was not configured correctly following the activation of SR-IOV.
New Functions
1.None.
Upgrade recommendations
Upgrade the driver,as a best practice.
Problems Solved
1.Fixed the problem that the driver did not consider whether the device was in the disassembly or detection process when performing recovery operations, which would cause a kernel crash
2.Fixed the problem that setting the rdma_cm RoCE static rate to 0 would lead to high storage IO latency when a large number of rdma_cm connections were established
3.Fixed the issue that the "rdma res show qp" command would return an "Invalid argument" error when there were a large number of QPs
4.Upgrade knem to support RHEL 8.7 system, so as to avoid the problem of call tracking caused by soft lock
5.Fixed an issue where the system might hang during startup after loading the mlx5_core driver in some systems with multiple ConnectX adapters
6.Added support for using VF directly and VF assigned to QEMU to use Relaxed Ordering. Relaxed Ordering can improve performance under certain settings. But so far, it's only available in PF.
New Functions
1.Added support for RHEL 9.2, RHEL 8.8, SLES15-SP5, KYLIN10-SP3 networks.
Upgrade recommendations
Upgrade the driver,as a best practice.
Problems Solved
1.The knem-dkms package explicitly requires GCC to build the knem driver (at install times). Under some circumstances, on Debian systems, the apt install method may result in a system that has only gcc-<version> (e.g., gcc-10) installed.
2.The host driver probe did not check whether there are existing SFs which are present in the device, causing the host driver to not recreate those SFs.
3.Installing MLNX_OFED_LINUX on an Ubuntu system with CUDA (version < 11.6) may result in an automatic installation of the ucx-cuda package that will fail with an error message in the log file ucx-cuda.debinstall.log about missing dependencies.
4. When using BlueField with old kernels, multiple OVS meter do not work.
5.Upgrading from version 5.6-2 to 5.7 failed.
6.Starting firmware version xx.34.0350, a new NVCONFIG has been added to the ARM side only: MANAGEMENT_PF_MODE.If this config is on, the user will see a PCI Function (PF) which failed to probe:
[ 6.837102] mlx5_core 0000:03:00.2: mlx5_cmd_check:756:(pid 206): ENABLE_HCA(0x104) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x6ca1f5)
[ 6.864227] mlx5_core 0000:03:00.2: mlx5_peer_pf_init:40:(pid 206): Failed to enable peer PF HCA err(-22)
[ 6.883453] mlx5_core 0000:03:00.2: mlx5_load:1129:(pid 206): Failed to init embedded CPU
[ 8.261268] mlx5_core 0000:03:00.2: init_one:1365:(pid 206): mlx5_load_one failed with error code -22
[ 8.280056] mlx5_core: probe of 0000:03:00.2 failed with error -22
7.Upgrading from version 5.6-2 to 5.7 failed.
8.When using sysfs to read the hash function used to distribute the traffic between the TIRs (Transport Interface Receive), on occasion, the server crashed.
9.STP packets failed to be transmitted.
10.HW-GRO feature was blocked due to firmware limitations.
11.In older kernel version, PTP was not supported over VLAN interfaces.
12.The rdma res show cm_id command does not list all cm_ids when some of them are in LISTEN state.
13.Creating and deleting MRs, caused a kernel slab cache leak issue.
New Functions
1.[All HCAs] Removed dependency between SR-IOV and eSwitch mode. Currently, there are three eSwitch modes: none, legacy, and switchdev (non of which are the default mode). When disabling SR-IOV, the current eSwitch mode will be changed to none. This feature removes eSwitch mode none and also removes dependency between SR-IOV and eSwitch mode.
2.[All HCAs] Added support for running DevLink commands in parallel on different DevLink devices is possible. For example, burning firmware on a few cards on the same host in parallel using DevLink API is now possible.
Login