Files
kernel/kernel-modules/mlnx-ofa_kernel/debian/patches/0001-Enable-mlx5-onboard-udev-name.patch
Jiping Ma 4653f78aa3 kernel-modules: re-enable mlnx-ofa_kernel
This commit re-enables mlnx-ofa_kernel OOT drivers and disables the
in-tree bnxt_en/bnxt_re and mlnx-ofa_kernel drivers because we decide
to select the OOT drivers for bnxt_en/bnxt_re and mlnx-ofa_kernel based
on Melanox/Broadcom's suggestion.

We also upgrade the driver version recommended by Nvidia. Upgrade
the mlnx-ofa_kernel to the version 23.10.2.1.3.1 from 5.9, also upgrade
the rdma-core to the version 2307mlnx47 from 59mlnx44.

This commit also corrects one small patch naming issue, deletes 'i' in
the patch name.

The new versions are:
mlnx-ofa_kernel-23.10.tgz
rdma-core-2307mlnx47.tar.gz

Verification:
  - Build package success for rdma-core, mlnx-ofa_kernel.
  - Install onto a StarlingX system with All-in-One lab with network
    adapters Mellanox's OFED. The network adapters of controllers
    are Mellanox Technologies MT27800 Family [ConnectX-5].
  - The physical function interfaces are up and pass packets for rt
    and std.
  - create vfs, ensure that the interface can come up and pass packets.
  - RDMA/Infiniband over Ethernet functionalities of the Mellanox
    adapters were successfully tested using the Linux RDMA community's
    perftest package.

Story: 2011056
Task: 49876

Depends-On: https://review.opendev.org/c/starlingx/root/+/916966
Change-Id: I0f88125f1332451127947763088c193fc9342405
Signed-off-by: Jiping Ma <jiping.ma2@windriver.com>
2024-04-25 08:03:45 -04:00

63 lines
2.2 KiB
Diff

From c6a43833d3b9bf97049e373d20a6eb7daff91c36 Mon Sep 17 00:00:00 2001
From: Steven Webster <steven.webster@windriver.com>
Date: Thu, 11 Aug 2022 12:32:48 -0400
Subject: [PATCH] Enable mlx5 onboard udev name
This patch prioritizes the udev renaming rule for mlx5 controlled
devices to take the onboard name over the slot/path name.
This is consistent with the 70-persistent-net.rules file written
by the StarlingX installer.
It is also consistent with the naming order in the 99-default.link
file.
Without this patch, there could be an inconsistency with the
70-persistent-net.rules first re-naming the device to its
slot/path name, and then being overridden by the Mellanox specific
82-net-setup-link.rules.
Signed-off-by: Steven Webster <steven.webster@windriver.com>
[jm: Adapted the patch for context change]
Signed-off-by: Jiping Ma <jiping.ma2@windriver.com>
---
ofed_scripts/vf-net-link-name.sh | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/ofed_scripts/vf-net-link-name.sh b/ofed_scripts/vf-net-link-name.sh
index e22ae76..1134629 100755
--- a/ofed_scripts/vf-net-link-name.sh
+++ b/ofed_scripts/vf-net-link-name.sh
@@ -93,7 +93,9 @@ function test_if_pf() {
}
if [ "$skip" == "0" ]; then
- if [ -n "$ID_NET_NAME_SLOT" ]; then
+ if [ -n "$ID_NET_NAME_ONBOARD" ]; then
+ NAME="${ID_NET_NAME_ONBOARD%%np[[:digit:]]}"
+ elif [ -n "$ID_NET_NAME_SLOT" ]; then
NAME="${ID_NET_NAME_SLOT%%np[[:digit:]]}"
elif [ -n "$ID_NET_NAME_PATH" ]; then
NAME="${ID_NET_NAME_PATH%%np[[:digit:]]}"
@@ -226,11 +228,14 @@ for cnt in {1..2}; do
continue
fi
- parent_path=`get_pci_name $pci ID_NET_NAME_SLOT`
+ parent_path=`get_pci_name $pci ID_NET_NAME_ONBOARD`
if [ -z "$parent_path" ]; then
- parent_path=`get_pci_name $pci ID_NET_NAME_PATH`
+ parent_path=`get_pci_name $pci ID_NET_NAME_SLOT`
if [ -z "$parent_path" ]; then
- continue
+ parent_path=`get_pci_name $pci ID_NET_NAME_PATH`
+ if [ -z "$parent_path" ]; then
+ continue
+ fi
fi
fi
echo "NAME=${parent_path}_$PORT"
--
2.43.0