> -----Original Message-----
> From: BillZhou <do...@mellanox.com>
> Sent: Friday, April 10, 2020 12:47 PM
> To: Matan Azrad <ma...@mellanox.com>; Bill Zhou <do...@mellanox.com>;
> Ori Kam <or...@mellanox.com>; wenzhuo...@intel.com;
> jingjing...@intel.com; bernard.iremon...@intel.com;
> john.mcnam...@intel.com; marko.kovace...@intel.com; Thomas Monjalon
> <tho...@monjalon.net>; ferruh.yi...@intel.com; arybche...@solarflare.com
> Cc: dev@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 <do...@mellanox.com>
> ---
Nice patch.
Acked-by: Ori Kam <or...@mellanox.com>
Thanks,
Ori
