Skip to content

net/mlx5/hws: fix matcher clean up for FDB tables

Dariusz Sosnowski dpdk-dev 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 2 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2net/mlx5/hws: fix order of destroying default tablesdrivers/net/mlx5/hws/mlx5dr_table.c+1 -10 replies
2/2net/mlx5/hws: fix disconnecting matcherdrivers/net/mlx5/hws/mlx5dr_matcher.c+35 -00 replies

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by.

PatchAlex VeskerMatan Azrad
SeriesSeries-acked-by
1/2R-b
2/2R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/2] net/mlx5/hws: fix matcher clean up for FDB tables

Before these patches, if an application was configured to run with HW Steering and E-Switch enabled, on EAL cleanup the assertion in mlx5_dev_hw_global_release() was triggered - PD release was unsuccessful.

Root cause of this issue was linked to an inability to destroy RTC objects used internally in mlx5, in HW Steering implementation.
PMD was unable to destroy RTC objects, because of dangling references to those objects. More specifically, if all matchers connected to a single flow table were created, this flow table was still referencing RTC objects when theye were being destroyed.

This patch series fixes that behavior.
Matcher uninitilization is updated to remove the references to RTC objects from flow table object if the last matcher related to the flow table was destroyed.

Erez Shitrit (2):
net/mlx5/hws: fix order of destroying default tables net/mlx5/hws: fix disconnecting matcher

 drivers/net/mlx5/hws/mlx5dr_matcher.c | 35 +++++++++++++++++++++++++++
 drivers/net/mlx5/hws/mlx5dr_table.c   |  2 +-
 2 files changed, 36 insertions(+), 1 deletion(-)
Signature · 1 line
2.25.1