Hi,
> -----Original Message-----
> From: Michael Baum <michae...@nvidia.com>
> Sent: Wednesday, February 28, 2024 11:51 AM
> To: dev@dpdk.org
> Cc: Matan Azrad <ma...@nvidia.com>; Dariusz Sosnowski
> <dsosnow...@nvidia.com>; Raslan Darawsheh <rasl...@nvidia.com>; Slava
> Ovsiienko <viachesl...@nvidia.com>; Ori Kam <or...@nvidia.com>;
> Suanming Mou <suanmi...@nvidia.com>; Alex Vesker <va...@nvidia.com>;
> sta...@dpdk.org; Erez Shitrit <ere...@nvidia.com>
> Subject: [PATCH] net/mlx5/hws: enable multiple integrity items
>
> The integrity item uses the DW "oks1" in header layout. It includes the all
> supported bits for both inner and outer. When item is integrity type, the
> relevant bits are turned on and all DW is submitted.
>
> When user provides more then single integrity item in same pattern, the last
> one overrides the values were submitted before. This is problematic when user
> wants to match integrity bits for both inner and outer in same pattern, he
> cannot merge them into single item since rte_flow API provides encapsulation
> level field to match either inner or outer.
>
> This patch avoids the overriding values, when "oks1" is submitted, operator
> "or" is used instead of regular set.
>
> Fixes: c55c2bf35333 ("net/mlx5/hws: add definer layer")
> Cc: va...@nvidia.com
> Cc: sta...@dpdk.org
>
> Signed-off-by: Michael Baum <michae...@nvidia.com>
> Reviewed-by: Erez Shitrit <ere...@nvidia.com>
> Acked-by: Matan Azrad <ma...@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
