On 4/21/2020 11:11 AM, Bill Zhou wrote:
> From: Dong Zhou <do...@mellanox.com>
>
> One of the reasons to destroy a flow is the fact that no packet matches the
> flow for "timeout" time.
> For example, when TCP\UDP sessions are suddenly closed.
>
> Currently, there is not any DPDK mechanism for flow aging and the
> applications use their own ways to detect and destroy aged-out flows.
>
> The flow aging implementation need include:
> - A new rte_flow action: RTE_FLOW_ACTION_TYPE_AGE to set the timeout and
> the application flow context for each flow.
> - A new ethdev event: RTE_ETH_EVENT_FLOW_AGED for the driver to report
> that there are new aged-out flows.
> - A new rte_flow API: rte_flow_get_aged_flows to get the aged-out flows
> contexts from the port.
> - Support input flow aging command line in Testpmd.
>
> The new event type addition in the enum is flagged as an ABI breakage, so
> an ignore rule is added for these reasons:
> - It is not changing value of existing types (except MAX)
> - The new value is not used by existing API if the event is not registered
> In general, it is safe adding new ethdev event types at the end of the
> enum, because of event callback registration mechanism.
>
> Signed-off-by: Dong Zhou <do...@mellanox.com>
Carrying ack from prev versions:
Acked-by: Ori Kam <or...@mellanox.com>
Acked-by: Andrew Rybchenko <arybche...@solarflare.com>
Acked-by: Jerin Jacob <jer...@marvell.com>
Acked-by: Matan Azrad <ma...@mellanox.com>
Applied to dpdk-next-net/master, thanks.
