The eventdev API was introduced in DPDK 17.05 release.
Since then it
- has been reviewed and iterated for 17.08, 17.11 releases
- three drivers were implemented using the API.
- introduced another subsystem like service core and ethdev-eventdev Rx
adapter APIs to abstract the difference between HW and SW
eventdev implementations in a transparent way.
- had extensive use by the app/test-eventdev/ and
examples/eventdev_pipeline_sw_pmd/
I believe the API is now stable and the EXPERIMENTAL label
should be removed.
CC: Bruce Richardson <bruce.richard...@intel.com>
CC: Harry van Haaren <harry.van.haa...@intel.com>
CC: Gage Eads <gage.e...@intel.com>
CC: Hemant Agrawal <hemant.agra...@nxp.com>
CC: Nipun Gupta <nipun.gu...@nxp.com>
CC: Nikhil Rao <nikhil....@intel.com>
CC: Pavan Nikhilesh <pbhagavat...@caviumnetworks.com>
CC: Thomas Monjalon <tho...@monjalon.net>
Signed-off-by: Jerin Jacob <jerin.ja...@caviumnetworks.com>
---
There are two more outstanding eventdev API changes. Please find below.
Please express if you have any concern in changing those APIs. I would
like to fix this API issue and remove experimental tag in v17.11,
if we all agree.
- evendev: fix inconsistency in event queue config
http://dpdk.org/dev/patchwork/patch/30293/
- remove rte_event_schedule() API and use service core infrastructure
http://dpdk.org/dev/patchwork/patch/30375/
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2a58378b7..4a4be3a54 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -262,7 +262,7 @@ F: lib/librte_cryptodev/
F: test/test/test_cryptodev*
F: examples/l2fwd-crypto/
-Eventdev API - EXPERIMENTAL
+Eventdev API
M: Jerin Jacob <jerin.ja...@caviumnetworks.com>
T: git://dpdk.org/next/dpdk-next-eventdev
F: lib/librte_eventdev/
--
2.14.2
