On Thu, Dec 21, 2017 at 4:35 AM, Qi Zhang <qi.z.zh...@intel.com> wrote: > Add new APIs to support flow timeout, application is able to > 1. Setup the time duration of a flow, the flow is expected to be deleted > automatically when timeout.
Can you explain how the application (OVS) is expected to use this API? It will help to better understand the motivation here... Are you trying to move the aging timer from application code into the PMD? or can your HW remove/disable/inactivate a flow at certain time semantics without software context? I would prefer to have the aging timer logic in a centralized location, leek the application itself or some DPDK library. instead of having each PMD implement its own software timers. > 3. Register a callback function when a flow is deleted due to timeout. Is the application 'struct rte_flow*' handle really deleted? or the flow was removed from HW, just in-active at this time? Can a flow be re-activated? or does this require a call to rte_flow_destory() and ret_flow_create()? Alex
