[PATCH] net/mlx5/hws: enable multiple integrity items

[Raslan Darawsheh]

Hi,

> -----Original Message-----
> From: Michael Baum <michaelba at nvidia.com>
> Sent: Wednesday, February 28, 2024 11:51 AM
> To: dev at dpdk.org
> Cc: Matan Azrad <matan at nvidia.com>; Dariusz Sosnowski
> <dsosnowski at nvidia.com>; Raslan Darawsheh <rasland at nvidia.com>; Slava
> Ovsiienko <viacheslavo at nvidia.com>; Ori Kam <orika at nvidia.com>;
> Suanming Mou <suanmingm at nvidia.com>; Alex Vesker <valex at nvidia.com>;
> stable at dpdk.org; Erez Shitrit <erezsh at 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: valex at nvidia.com
> Cc: stable at dpdk.org
> 
> Signed-off-by: Michael Baum <michaelba at nvidia.com>
> Reviewed-by: Erez Shitrit <erezsh at nvidia.com>
> Acked-by: Matan Azrad <matan at nvidia.com>
Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh