Re: [RFC 2/2] ethdev: queue-based flow aged report

2022-05-31 Thread Thomas Monjalon
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 se

Re: [RFC 2/2] ethdev: queue-based flow aged report

2022-05-31 Thread Jack Min
On 5/31/22 00:42, Thomas Monjalon wrote: 07/04/2022 07:30, Xiaoyu Min: When application use queue-based flow management and operate the same flow on the same queue, e.g create/destroy/query, API for querying aged flows should also with queue id parameter just like other queue-based flow APIs. A

Re: [RFC 2/2] ethdev: queue-based flow aged report

2022-05-30 Thread Thomas Monjalon
07/04/2022 07:30, Xiaoyu Min: > When application use queue-based flow management and operate the same > flow on the same queue, e.g create/destroy/query, API for querying aged > flows should also with queue id parameter just like other queue-based > flow APIs. A verb is missing, I am not sure to u

[RFC 2/2] ethdev: queue-based flow aged report

2022-04-06 Thread Xiaoyu Min
When application use queue-based flow management and operate the same flow on the same queue, e.g create/destroy/query, API for querying aged flows should also with queue id parameter just like other queue-based flow APIs. By this way, PMD can work in more optimized way since resources are isolate