DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kinsella, Ray" <mdr@ashroe.eu>
To: dpdk-dev <dev@dpdk.org>, "Walsh, Conor" <conor.walsh@intel.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Zhihong Wang <zhihong.wang@intel.com>,
	Chenbo Xia <chenbo.xia@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Fiona Trahe <fiona.trahe@intel.com>,
	Ashish Gupta <ashish.gupta@marvell.com>,
	Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	Ori Kam <orika@mellanox.com>,
	Declan Doherty <declan.doherty@intel.com>,
	Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	"Iremonger, Bernard" <bernard.iremonger@intel.com>,
	Kevin Laatz <kevin.laatz@intel.com>,
	Olivier Matz <olivier.matz@6wind.com>,
	Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Ruifeng Wang <Ruifeng.Wang@arm.com>
Subject: [dpdk-dev] DPDK Experimental Functions
Date: Thu, 27 Aug 2020 14:00:19 +0100	[thread overview]
Message-ID: <eee4e61b-7d6b-d224-0496-ac263b2c1af1@ashroe.eu> (raw)

Hi All,

During recent work on the DPDK ABI, where we are looking to develop a nightly ABI regression test. 

We found a large number of experimental functions currently in DPDK API.
Currently, there are 537 experimental APIs out of a total of roughly ~1800 API, 30%-ish. 

While there is no correct number, as a percentage of the total, this appears to be very high.
I would question if all these API are really "new" and warrant the status?

There are currently 38 libraries and drivers with experimental functions.
And to be fair there are number of recently added libraries in list, shown below.
However there are also a number of libraries that have been around a very long time.

The following libraries and drivers have 10 or more experimental functions:

1.	rte_eal: 119
2.	rte_ethdev: 43
3.	rte_vhost: 42
4.	rte_graph: 35 (EXPERIMENTAL)
5.	rte_compressdev: 34
6.	rte_rib: 28 (EXPERIMENTAL)
7.	rte_pipeline: 24
8.	rte_regexdev: 22 (EXPERIMENTAL)
9.	rte_cryptodev: 18
10.	rte_fib: 16 (EXPERIMENTAL)
11.	rte_ipsec: 15 (EXPERIMENTAL)
12.	rte_telemetry: 12 (EXPERIMENTAL)
13.	rte_mbuf: 11
14.	rte_rcu: 11 (EXPERIMENTAL)
15.	rte_bus_fslmc: 11
16.	rte_bpf: 10 (EXPERIMENTAL)

Do the maintainers of these libraries and drivers, 
A. Feel that experimental status continues to be warranted against these API?
B. Have plans in place to move all/some of these functions to stable in the 20.11 timeframe?

Kudos to Conor Walsh for pulling this data together. 

Thanks,

Ray K

             reply	other threads:[~2020-08-27 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 13:00 Kinsella, Ray [this message]
2020-09-01 13:39 ` Thomas Monjalon
2020-09-03 10:01   ` Lukasz Wojciechowski
2020-09-03 10:07   ` Lukasz Wojciechowski
2020-09-04  4:48 ` Honnappa Nagarahalli
2020-09-04  5:58   ` Hemant Agrawal

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=eee4e61b-7d6b-d224-0496-ac263b2c1af1@ashroe.eu \
    --to=mdr@ashroe.eu \
    --cc=Ruifeng.Wang@arm.com \
    --cc=arybchenko@solarflare.com \
    --cc=ashish.gupta@marvell.com \
    --cc=bernard.iremonger@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=conor.walsh@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=fiona.trahe@intel.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=kevin.laatz@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=olivier.matz@6wind.com \
    --cc=orika@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=vladimir.medvedkin@intel.com \
    --cc=zhihong.wang@intel.com \
    /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).