These 2 patches are a suggestion to add a hint to the struct rte_event_port_conf.event_port_cfg.
The usage of these hints is to allow an application to identify/communicate to the PMD what ports will primarily serve what purpose. E.g, some ports are "mainly producers" in that they are usually polling Ethdev RXQs (or other event sources..) and enqueue the resulting events to the eventdev instance. Similarly there are usages for "worker" (mainly forwards events) and "consumer" (mainly consumes events without re-enq). Note that these flags are *hints* only, and *functionally* any combination of (NEW/FWD/RELEASE) is still allowed by any port. The reason to add these is to allow a PMD to allocate internal resource more efficiently. Note that this implementation does not change the ABI, as it gives a purpose to existing bits in an existing field. Regards, -Harry Harry van Haaren (2): lib/eventdev: add usage hints to port configure API examples/eventdev_pipeline: use port config hints .../pipeline_worker_generic.c | 2 ++ .../eventdev_pipeline/pipeline_worker_tx.c | 2 ++ lib/eventdev/rte_eventdev.h | 23 +++++++++++++++++++ 3 files changed, 27 insertions(+) -- 2.30.2
