DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: dev@dpdk.org
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Harry van Haaren <harry.van.haaren@intel.com>,
	Gage Eads <gage.eads@intel.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Nipun Gupta <nipun.gupta@nxp.com>,
	Nikhil Rao <nikhil.rao@intel.com>,
	Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev]  [PATCH] eventdev: remove experimental label
Date: Mon, 16 Oct 2017 16:02:55 +0530	[thread overview]
Message-ID: <20171016103255.16322-1-jerin.jacob@caviumnetworks.com> (raw)

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.richardson@intel.com>
CC: Harry van Haaren <harry.van.haaren@intel.com>
CC: Gage Eads <gage.eads@intel.com>
CC: Hemant Agrawal <hemant.agrawal@nxp.com>
CC: Nipun Gupta <nipun.gupta@nxp.com>
CC: Nikhil Rao <nikhil.rao@intel.com>
CC: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
CC: Thomas Monjalon <thomas@monjalon.net>
Signed-off-by: Jerin Jacob <jerin.jacob@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.jacob@caviumnetworks.com>
 T: git://dpdk.org/next/dpdk-next-eventdev
 F: lib/librte_eventdev/
-- 
2.14.2

             reply	other threads:[~2017-10-16 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 10:32 Jerin Jacob [this message]
2017-10-23 18:27 ` Eads, Gage
2017-10-30 17:38   ` Jerin Jacob
2017-11-01 14:12     ` Eads, Gage
2017-11-02  4:11       ` Jerin Jacob
2017-11-02 14:19         ` Eads, Gage
2017-11-07 22:16           ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171016103255.16322-1-jerin.jacob@caviumnetworks.com \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gage.eads@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=nikhil.rao@intel.com \
    --cc=nipun.gupta@nxp.com \
    --cc=pbhagavatula@caviumnetworks.com \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).