31/05/2022 13:06, Jack Min: > On 5/31/22 00:42, Thomas Monjalon wrote: > > 07/04/2022 07:30, Xiaoyu Min: > >> + * If queue-based flow rule management is used and port configured with > >> + * flag RTE_FLOW_PORT_FLAG_STRICT_QUEUE, RTE_ETH_EVENT_FLOW_AGED event > >> + * is triggered with ret_param set to the corresponding flow queue when > >> + * a flow queue detects new aged-out flows. > > > > Are you sure it is a good idea to use ret_param for such data? > > Well, it seems the only way to add queue information without add/change > APIs. > > > ret_param of an event is supposed to be used by the driver > > to get a confirmation from the application. > > > > If the application needs extra info of an event, > > it is better to do a separate query like rte_flow_get_aged_flows(). > > Ok, since the *ret_param* is supposed to be used by driver, then the > above approach is not a good idea. > > So we need a new API, something like rte_flow_get_aged_event_queues(), > which will return > > all flow queues which has the aged flows, right?
Yes, a new function seems required.
