summaryrefslogtreecommitdiff
path: root/drivers/net/mlx5/mlx5_txq.c
diff options
context:
space:
mode:
authorViacheslav Ovsiienko <viacheslavo@mellanox.com>2019-09-25 07:53:24 +0000
committerFerruh Yigit <ferruh.yigit@intel.com>2019-10-07 15:00:58 +0200
commit46e10a4c1b87f08316702d2a43301199858f0597 (patch)
tree4d41d37edded49be24439796090028ac5bd7e8af /drivers/net/mlx5/mlx5_txq.c
parentfd88e7401230a4eb6208c9a07540bf9d13c76691 (diff)
downloaddpdk-next-eventdev-46e10a4c1b87f08316702d2a43301199858f0597.zip
dpdk-next-eventdev-46e10a4c1b87f08316702d2a43301199858f0597.tar.gz
dpdk-next-eventdev-46e10a4c1b87f08316702d2a43301199858f0597.tar.xz
net/mlx5: move backing PCI device to private context
Now all devices created over the same multiport IB device have shared context containing the backing PCI device field. For the VF LAG configurations it becomes possible the representors might be connected to VF created over different PFs. In this case representors have the different backing PCI devices and mentioned field should be moved to device private area. Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com> Acked-by: Matan Azrad <matan@mellanox.com>
Diffstat (limited to 'drivers/net/mlx5/mlx5_txq.c')
-rw-r--r--drivers/net/mlx5/mlx5_txq.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/mlx5/mlx5_txq.c b/drivers/net/mlx5/mlx5_txq.c
index 2b7d6c0..d9fd143 100644
--- a/drivers/net/mlx5/mlx5_txq.c
+++ b/drivers/net/mlx5/mlx5_txq.c
@@ -728,7 +728,7 @@ txq_set_params(struct mlx5_txq_ctrl *txq_ctrl)
if (config->txqs_inline == MLX5_ARG_UNSET)
txqs_inline =
#if defined(RTE_ARCH_ARM64)
- (priv->sh->pci_dev->id.device_id ==
+ (priv->pci_dev->id.device_id ==
PCI_DEVICE_ID_MELLANOX_CONNECTX5BF) ?
MLX5_INLINE_MAX_TXQS_BLUEFIELD :
#endif