RE: [PATCH v6 03/18] net/mlx5: add shared header reformat support

[Slava Ovsiienko]

> -----Original Message-----
> From: Suanming Mou <suanmi...@nvidia.com>
> Sent: Thursday, October 20, 2022 18:42
> To: Matan Azrad <ma...@nvidia.com>; Slava Ovsiienko <viachesl...@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasl...@nvidia.com>; Ori Kam
> <or...@nvidia.com>
> Subject: [PATCH v6 03/18] net/mlx5: add shared header reformat support
> 
> As the rte_flow_async API defines, the action mask with field value not be 0
> means the action will be used as shared in all the flows in the table.
> 
> The header reformat action with action mask field not be 0 will be created
> as constant shared action. For encapsulation header reformat action, there
> are two kinds of encapsulation data, raw_encap_data and rte_flow_item
> encap_data. Both of these two kinds of data can be identified from the
> action mask conf as constant or not.
> 
> Examples:
> 1. VXLAN encap (encap_data: rte_flow_item)
>       action conf (eth/ipv4/udp/vxlan_hdr)
> 
>       a. action mask conf (eth/ipv4/udp/vxlan_hdr)
>         - items are constant.
>       b. action mask conf (NULL)
>         - items will change.
> 
> 2. RAW encap (encap_data: raw)
>       action conf (raw_data)
> 
>       a. action mask conf (not NULL)
>         - encap_data constant.
>       b. action mask conf (NULL)
>         - encap_data will change.
> 
> Signed-off-by: Suanming Mou <suanmi...@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viachesl...@nvidia.com>