Hi,

> -----Original Message-----
> From: Jiawei(Jonny) Wang <jiaw...@nvidia.com>
> Sent: Wednesday, March 9, 2022 12:20 PM
> 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>;
> sta...@dpdk.org
> Subject: [PATCH] net/mlx5: fix the sample flow failure on the trusted device
> 
> The flow with sample action will be split into two sub flows,
> and a tag action was added implicitly in the sample prefix sub flow,
> the reserved metadata regC index was used for this tag action.
> 
> The reserved metadata regC was shared with metering action,
> for Connect-5 trusted device(VF/SF), the reserved metadata regC was
> invalid since PF only supported the legacy metering.
> 
> This patch adds the checking for the tag index and back to use the
> application tag if a failure happened.
> 
> Fixes: a9b6ea45bed6 ("net/mlx5: fix tag ID conflict with sample action")
> Cc: sta...@dpdk.org
> 
> Signed-off-by: Jiawei Wang <jiaw...@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viachesl...@nvidia.com>

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

Reply via email to