net/mlx5: add limitation for E-Switch Manager match

For BF with old FW which doesn't expose the E-Switch Manager vport ID,
E-Switch Manager port matching works correctly only when BF is in
embedded CPU mode.

This patch adds the limitation description.

Fixes: a564038699f9 ("net/mlx5: support E-Switch manager egress traffic match")
Cc: stable@dpdk.org

Signed-off-by: Shun Hao <shunh@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
This commit is contained in:
Shun Hao 2022-06-19 06:21:27 +03:00 committed by Raslan Darawsheh
parent 57d6a458a8
commit 68e9925c30
3 changed files with 18 additions and 2 deletions

View File

@ -358,6 +358,12 @@ Limitations
- can be applied to VF ports only.
- must specify PF port action (packet redirection from VF to PF).
- E-Switch Manager matching:
- For Bluefield with old FW
which doesn't expose the E-Switch Manager vport ID in the capability,
matching E-Switch Manager should be used only in Bluefield embedded CPU mode.
- Raw encapsulation:
- The input buffer, used as outer header, is not validated.

View File

@ -2076,4 +2076,8 @@ int flow_dv_action_query(struct rte_eth_dev *dev,
size_t flow_dv_get_item_hdr_len(const enum rte_flow_item_type item_type);
int flow_dv_convert_encap_data(const struct rte_flow_item *items, uint8_t *buf,
size_t *size, struct rte_flow_error *error);
#define MLX5_PF_VPORT_ID 0
#define MLX5_ECPF_VPORT_ID 0xFFFE
#endif /* RTE_PMD_MLX5_FLOW_H_ */

View File

@ -99,6 +99,7 @@ flow_dv_get_esw_manager_vport_id(struct rte_eth_dev *dev)
struct mlx5_priv *priv = dev->data->dev_private;
struct mlx5_common_device *cdev = priv->sh->cdev;
/* New FW exposes E-Switch Manager vport ID, can use it directly. */
if (cdev->config.hca_attr.esw_mgr_vport_id_valid)
return (int16_t)cdev->config.hca_attr.esw_mgr_vport_id;
@ -108,9 +109,14 @@ flow_dv_get_esw_manager_vport_id(struct rte_eth_dev *dev)
case PCI_DEVICE_ID_MELLANOX_CONNECTX5BF:
case PCI_DEVICE_ID_MELLANOX_CONNECTX6DXBF:
case PCI_DEVICE_ID_MELLANOX_CONNECTX7BF:
return (int16_t)0xfffe;
/*
* In old FW which doesn't expose the E-Switch Manager vport ID in the capability,
* only the BF embedded CPUs control the E-Switch Manager port. Hence,
* ECPF vport ID is selected and not the host port (0) in any BF case.
*/
return (int16_t)MLX5_ECPF_VPORT_ID;
default:
return 0;
return MLX5_PF_VPORT_ID;
}
}