Hi,
> -----Original Message-----
> From: Gregory Etelson <getel...@nvidia.com>
> Sent: Thursday, March 7, 2024 12:19 PM
> To: dev@dpdk.org
> Cc: Gregory Etelson <getel...@nvidia.com>; Maayan Kashani
> <mkash...@nvidia.com>; Raslan Darawsheh <rasl...@nvidia.com>;
> sta...@dpdk.org; Dariusz Sosnowski <dsosnow...@nvidia.com>; Slava
> Ovsiienko <viachesl...@nvidia.com>; Ori Kam <or...@nvidia.com>;
> Suanming Mou <suanmi...@nvidia.com>; Matan Azrad
> <ma...@nvidia.com>; Alexander Kozyrev <akozy...@nvidia.com>
> Subject: [PATCH v2 2/3] net/mlx5: fix sync meter processing in HWS setup
>
> Synchronous calls for meter ASO try to pull pending completions from CQ,
> submit WR and return to caller. That avoids delays between WR post and HW
> response.
> If the template API was activated, PMD will use control queue for sync
> operations.
>
> PMD has different formats for the `user_data` context in sync and async meter
> ASO calls.
> PMD port destruction procedure submits async operations to the port control
> queue and polls the queue CQs to clean HW responses.
>
> Port destruction can pull a meter ASO completion from control CQ.
> Such completion has sync format, but was processed by async handler.
>
> The patch implements sync meter ASO interface with async calls in the
> template API environment.
>
> Fixes: 48fbb0e93d06 ("net/mlx5: support flow meter mark indirect action
> with HWS")
>
> Cc: sta...@dpdk.org
>
> Signed-off-by: Gregory Etelson <getel...@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnow...@nvidia.com>
> ---
> drivers/net/mlx5/mlx5.h | 35 +++++-
> drivers/net/mlx5/mlx5_flow_aso.c | 178 ++++++++++++++++++-----------
> drivers/net/mlx5/mlx5_flow_hw.c | 99 ++++++++--------
> drivers/net/mlx5/mlx5_flow_meter.c | 27 +++--
> 4 files changed, 216 insertions(+), 123 deletions(-)
Series applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
