On Fri, Apr 10, 2020 at 5:38 PM Andrew Rybchenko <arybche...@solarflare.com> wrote: > > On 4/10/20 12:46 PM, BillZhou wrote: > > 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> > > Acked-by: Andrew Rybchenko <arybche...@solarflare.com>
Acked-by: Jerin Jacob <jer...@marvell.com> >
