[dpdk-dev] [PATCH] ethdev: support flow aging

[Ori Kam]

> -----Original Message-----
> From: BillZhou <dongz at mellanox.com>
> Sent: Friday, April 10, 2020 12:47 PM
> To: Matan Azrad <matan at mellanox.com>; Bill Zhou <dongz at mellanox.com>;
> Ori Kam <orika at mellanox.com>; wenzhuo.lu at intel.com;
> jingjing.wu at intel.com; bernard.iremonger at intel.com;
> john.mcnamara at intel.com; marko.kovacevic at intel.com; Thomas Monjalon
> <thomas at monjalon.net>; ferruh.yigit at intel.com; arybchenko at solarflare.com
> Cc: dev at dpdk.org
> Subject: [PATCH] ethdev: support flow aging
> 
> 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 no 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.
> 
> Signed-off-by: BillZhou <dongz at mellanox.com>
> ---

Nice patch.
Acked-by: Ori Kam <orika at mellanox.com>
Thanks,
Ori