[dpdk-dev] [PATCH] ethdev: support flow aging
Thomas Monjalon
thomas at monjalon.net
Fri Apr 10 12:14:26 CEST 2020
10/04/2020 11:46, BillZhou:
> 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>
I think you should insert a space in your name: Bill Zhou.
I find strange to associate "Bill Zhou" with "dongz" in your email.
Are you sure you don't want to mention "Dong"?
> + * Added support for flow Aging mechanism base on counter.
Aging -> aging
base -> based
counter -> hardware counter?
More information about the dev
mailing list