Hi,
> -----Original Message----- > From: Shun Hao <sh...@nvidia.com> > Sent: Saturday, September 17, 2022 9:02 AM > To: Slava Ovsiienko <viachesl...@nvidia.com>; Matan Azrad > <ma...@nvidia.com>; Ori Kam <or...@nvidia.com> > Cc: dev@dpdk.org; Raslan Darawsheh <rasl...@nvidia.com> > Subject: [PATCH v1 0/3] Fix meter hierarchy issue for represented port > > When the represented port item was introduced, there's an issue that if a > flow matching represented port item uses a meter hierarchy action, it will > fail > due to the represented port item not supported correctly in meter hierarchy > creation. > > This patch set is adding the correct handling to support represented port. > And there're some limitation for the support that when matching all ports, > the meter hierarchy should not contain any meter having drop count. > > Shun Hao (3): > net/mlx5: fix meter hierarchy with represented port item > net/mlx5: add meter flow limitation when matching all ports > net/mlx5: fix meter ID tag for meter hierarchy > > doc/guides/nics/mlx5.rst | 1 + > drivers/net/mlx5/mlx5.h | 2 + > drivers/net/mlx5/mlx5_flow.c | 27 +++++++++---- > drivers/net/mlx5/mlx5_flow.h | 4 ++ > drivers/net/mlx5/mlx5_flow_dv.c | 71 ++++++++++++++++++++++---------- > - > 5 files changed, 73 insertions(+), 32 deletions(-) > > -- > 2.20.0 Series applied to next-net-mlx, Kindest regards Raslan Darawsheh
