diff options
| author | Mark Bloch <mbloch@nvidia.com> | 2021-10-21 12:46:17 +0000 |
|---|---|---|
| committer | Saeed Mahameed <saeedm@nvidia.com> | 2021-11-30 22:35:04 -0800 |
| commit | 43a0696f11567278b9412f947e43dd7906c831a8 (patch) | |
| tree | 62df61aa8e90368c99d7aafc48de4b8a5cc56ed9 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 1e59b32e45e47c8ea5455182286ba010bfa87813 (diff) | |
net/mlx5: E-Switch, fix single FDB creation on BlueField
Always use MLX5_FLOW_TABLE_OTHER_VPORT flag when creating egress ACL
table for single FDB. Not doing so on BlueField will make firmware fail
the command. On BlueField the E-Switch manager is the ECPF (vport 0xFFFE)
which is filled in the flow table creation command but as the
other_vport field wasn't set the firmware complains about a bad parameter.
This is different from a regular HCA where the E-Switch manager vport is
the PF (vport 0x0). Passing MLX5_FLOW_TABLE_OTHER_VPORT will make the
firmware happy both on BlueField and on regular HCAs without special
condition for each.
This fixes the bellow firmware syndrome:
mlx5_cmd_check:819:(pid 571): CREATE_FLOW_TABLE(0x930) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x754a4)
Fixes: db202995f503 ("net/mlx5: E-Switch, add logic to enable shared FDB")
Signed-off-by: Mark Bloch <mbloch@nvidia.com>
Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions