> -Original Message-
> From: Bing Zhao
> Sent: Thursday, October 22, 2020 17:07
> To: viachesl...@mellanox.com; ma...@mellanox.com
> Cc: dev@dpdk.org; Ori Kam ; Raslan Darawsheh
>
> Subject: [PATCH v2 5/6] net/mlx5: change hairpin ingress flow validation
>
> In the current implementation
In the current implementation of the single port hairpin, there is a
implicit splitting process for actions. When inserting a hairpin
flow, all the actions will be included with the ingress attribute.
The flow engine will check and decide which actions should be moved
into the TX flow part, e.g., e
2 matches
Mail list logo