net/mlx5: fix switchdev mode recognition

The new kernels might add the switch_id attribute to the
Netlink replies and this caused the wrong recognition
of the E-Switch presence. The single uplink device was
erroneously recognized as master and it caused the
extending match for source vport index on all installed
flows, including the default ones, and adding extra hops
in the steering engine, that affected the maximal
throughput packet rate.

The extra check for the new device name format (it supposes
the new kernel) and the device is only one is added. If this
check succeeds the E-Switch presence is considered as wrongly
detected and overridden.

Fixes: 30a86157f6d5 ("net/mlx5: support PF representor")
Cc: stable@dpdk.org
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>

diff --git a/drivers/net/mlx5/linux/mlx5_os.c b/drivers/net/mlx5/linux/mlx5_os.c
index 534a56a..302a881 100644 (file)
--- a/drivers/net/mlx5/linux/mlx5_os.c
+++ b/drivers/net/mlx5/linux/mlx5_os.c
@@ -2298,6 +2298,18 @@ mlx5_os_pci_probe_pf(struct rte_pci_device *pci_dev,
                        ret = -rte_errno;
                        goto exit;
                }
+               /*
+                * New kernels may add the switch_id attribute for the case
+                * there is no E-Switch and we wrongly recognized the
+                * only device as master. Override this if there is the
+                * single device with single port and new device name
+                * format present.
+                */
+               if (nd == 1 &&
+                   list[0].info.name_type == MLX5_PHYS_PORT_NAME_TYPE_UPLINK) {
+                       list[0].info.master = 0;
+                       list[0].info.representor = 0;
+               }
        }
        MLX5_ASSERT(ns);
        /*