The software event dev is a centralized software scheduler and needs `rte_event_schedule` to be called repeatedly in order to distribute the events. In most cases, this requires a dedicated lcore to achieve this.
With the introduction to the rte_service concept, software eventdev driver can register event distribution as a service component and offload it to a service core. Thus removing the requirement of calling `rte_event_schedule` explicitly and abstracts the differences between HW and SW PMD to provide a single interface to the application. Pavan Nikhilesh (7): eventdev: add API to get service id event/sw: extend service capability app/test-eventdev: update app to use service cores test/eventdev: update test to use service core examples/eventdev: update sample app to use service eventdev: remove eventdev schedule API doc: update software event device app/test-eventdev/evt_common.h | 41 ++++++++++ app/test-eventdev/evt_options.c | 10 --- app/test-eventdev/test_order_atq.c | 6 ++ app/test-eventdev/test_order_common.c | 3 - app/test-eventdev/test_order_queue.c | 6 ++ app/test-eventdev/test_perf_atq.c | 6 ++ app/test-eventdev/test_perf_common.c | 21 ----- app/test-eventdev/test_perf_common.h | 1 + app/test-eventdev/test_perf_queue.c | 6 ++ doc/guides/eventdevs/sw.rst | 13 ++-- drivers/event/octeontx/ssovf_evdev.c | 1 - drivers/event/skeleton/skeleton_eventdev.c | 2 - drivers/event/sw/sw_evdev.c | 10 ++- examples/eventdev_pipeline_sw_pmd/main.c | 51 +++++++----- lib/librte_eventdev/rte_eventdev.c | 17 ++++ lib/librte_eventdev/rte_eventdev.h | 53 +++++++------ test/test/test_eventdev_sw.c | 120 ++++++++++++++++------------- 17 files changed, 223 insertions(+), 144 deletions(-) -- 2.7.4
