> -----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>; Dariusz Sosnowski <dsosnow...@nvidia.com>
> Subject: [PATCH v6 18/18] net/mlx5: create control flow rules with HWS
>
> From: Dariusz Sosnowski <dsosnow...@nvidia.com>
>
> This patch adds creation of control flow rules required to receive default
> traffic (based on port configuration) with HWS.
>
> Control flow rules are created on port start and destroyed on port stop.
> Handling of destroying these rules was already implemented before that
> patch.
>
> Control flow rules are created if and only if flow isolation mode is
> disabled and creation process goes as follows:
>
> - Port configuration is collected into a set of flags. Each flag
> corresponds to a certain Ethernet pattern type, defined by
> mlx5_flow_ctrl_rx_eth_pattern_type enumeration. There is a separate
> flag for VLAN filtering.
> - For each possible Ethernet pattern type and:
> - For each possible RSS action configuration:
> - If configuration flags do not match this combination, it is
> omitted.
> - A template table is created using this combination of pattern
> and actions template (templates are fetched from hw_ctrl_rx
> struct stored in port's private data).
> - Flow rules are created in this table.
>
> Signed-off-by: Dariusz Sosnowski <dsosnow...@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viachesl...@nvidia.com>
