Skip to content

RFC queue-based flow aged report

Xiaoyu Min dpdk-dev 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest0 of 2 patches 0 repliesNew

v2 from the cover letter

- Add new API for querying which queues have aged out flows instead of passing queue id via *ret_param* in event.
- Use bit flags instead of enum
- Fix typo and wording

Patches in v1 No applies recorded yet

None of the 2 patches the cover letter announces are in this archive.

Reviews trailers per patch

PatchOri Kam
SeriesA-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [RFC 0/2] queue-based flow aged report

For the queue-based flow managemnt, application can operate the same flow on the same queue.

For example, application create flow with age action, query aged flow, and destroy aged flow. All operations of flow happens on the same queue.

In this case, the PMD could be more optimized since all operations of the same flow happens in sequence.

The current flow aged report API hasn't queue parameter as same as other queue-based flow management API.

This RFC propose to add new flow aged report API with queue parameter. Keep the old one for compatibility.

v2:
- Add new API for querying which queues have aged out flows instead of passing queue id via *ret_param* in event.
- Use bit flags instead of enum
- Fix typo and wording

Xiaoyu Min (2):
ethdev: port flags for pre-configuration flow hints
ethdev: queue-based flow aged report

 lib/ethdev/rte_flow.h        | 93 ++++++++++++++++++++++++++++++++++++
 lib/ethdev/rte_flow_driver.h | 13 +++++
 2 files changed, 106 insertions(+)
Signature · 1 line
2.36.1