common/mlx5: fix obtaining IB device in LAG mode
PATCH 1/1 common/mlx5: fix obtaining IB device in LAG mode
In hardware LAG mode, both PFs are in the same E-Switch domain but the VFs are in the other domains. Moreover, VF has its own dedicated IB device.
When probing a VF created on the 1st PF, usually its PCIe address is the same as the PF's except the function part. Then there would be some wrong VF BDF match on the IB "bond" device due to incomplete comparison (we do not compare the function part of BDF for bonding devices to match all bonded PFs).
Adding one extra condition to check whether the current PCIe address device is a VF will solve the incorrect IB device recognition. Thus the full address comparison will be done.
--- drivers/common/mlx5/linux/mlx5_common_os.c | 16 +++++++++------- drivers/common/mlx5/mlx5_common.h | 2 +- drivers/common/mlx5/mlx5_common_pci.c | 2 +- 3 files changed, 11 insertions(+), 9 deletions(-)
drivers/common/mlx5/linux/mlx5_common_os.c +9 -7
@@ -555,7 +555,7 @@ mlx5_os_pd_prepare(struct mlx5_common_device *cdev) }static struct ibv_device * -mlx5_os_get_ibv_device (const struct rte_pci_addr *addr) +mlx5_os_get_ibv_device (const struct rte_pci_device *pci_dev) {int n;struct ibv_device **ibv_list = mlx5_glue->get_device_list (&n);
@@ -564,6 +564,8 @@ mlx5_os_get_ibv_device(const struct rte_pci_addr *addr)uint8_t guid2[32 ] = {0 };int ret1, ret2 =-1 ;struct rte_pci_addr paddr; +const struct rte_pci_addr *addr = &pci_dev->addr; +bool is_vf_dev =mlx5_dev_is_vf_pci (pci_dev);if (ibv_list ==NULL || !n) { rte_errno =ENOSYS ;
@@ -579,11 +581,11 @@ mlx5_os_get_ibv_device(const struct rte_pci_addr *addr)if (ret1 >0 ) ret2 =mlx5_get_device_guid (&paddr, guid2,sizeof (guid2));/* Bond device can bond secondary PCIe */ -if ((strstr (ibv_list[n]->name,"bond" ) && - ((ret1 >0 && ret2 >0 && !memcmp (guid1, guid2,sizeof (guid1))) || - (addr->domain == paddr.domain && addr->bus == paddr.bus && - addr->devid == paddr.devid))) || - !rte_pci_addr_cmp (addr, &paddr)) { +if ((strstr (ibv_list[n]->name,"bond" ) && !is_vf_dev && + ((ret1 >0 && ret2 >0 && !memcmp (guid1, guid2,sizeof (guid1))) || + (addr->domain == paddr.domain && addr->bus == paddr.bus && + addr->devid == paddr.devid))) || + !rte_pci_addr_cmp (addr, &paddr)) { ibv_match = ibv_list[n];break ; }
@@ -697,7 +699,7 @@ mlx5_os_get_ibv_dev(const struct rte_device *dev)struct ibv_device *ibv;if (mlx5_dev_is_pci (dev)) - ibv =mlx5_os_get_ibv_device (&RTE_DEV_TO_PCI_CONST (dev)->addr); + ibv =mlx5_os_get_ibv_device (RTE_DEV_TO_PCI_CONST (dev));else ibv =mlx5_get_aux_ibv_device (RTE_DEV_TO_AUXILIARY_CONST (dev));if (ibv ==NULL ) {
drivers/common/mlx5/mlx5_common.h +1 -1
@@ -600,7 +600,7 @@ mlx5_dev_is_pci(const struct rte_device *dev);*/ __rte_internal bool -mlx5_dev_is_vf_pci (struct rte_pci_device *pci_dev); +mlx5_dev_is_vf_pci (const struct rte_pci_device *pci_dev);__rte_internal int
drivers/common/mlx5/mlx5_common_pci.c +1 -1
@@ -109,7 +109,7 @@ mlx5_dev_is_pci(const struct rte_device *dev) }bool -mlx5_dev_is_vf_pci (struct rte_pci_device *pci_dev) +mlx5_dev_is_vf_pci (const struct rte_pci_device *pci_dev) {switch (pci_dev->id.device_id) {case PCI_DEVICE_ID_MELLANOX_CONNECTX4VF :
Signature · 1 line
2.34.1
Hi,
Quoted 22 lines
-----Original Message-----
From: Bing Zhao <[email protected]>
Sent: Friday, June 30, 2023 3:42 PM
To: Matan Azrad <[email protected]>; Slava Ovsiienko <[email protected]>; Ori Kam <[email protected]>; Suanming Mou <[email protected]>; Raslan Darawsheh <[email protected]>
Cc: [email protected]; Rongwei Liu <[email protected]>; [email protected]
Subject: [PATCH] common/mlx5: fix obtaining IB device in LAG modeIn hardware LAG mode, both PFs are in the same E-Switch domain but the VFs are in the other domains. Moreover, VF has its own dedicated IB device.
When probing a VF created on the 1st PF, usually its PCIe address is the same as the PF's except the function part. Then there would be some wrong VF BDF match on the IB "bond" device due to incomplete comparison (we do not compare the function part of BDF for bonding devices to match all bonded PFs).
Adding one extra condition to check whether the current PCIe address device is a VF will solve the incorrect IB device recognition. Thus the full address comparison will be done.
Quoted 7 lines
Fixes f956d3d4c33c ("net/mlx5: fix probing with secondary bondingmember")
Cc: [email protected]
Cc: [email protected]Signed-off-by Bing Zhao <[email protected]>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh