DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>
Cc: dev@dpdk.org, "Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: Remove EXPERIMENTAL label
Date: Tue, 05 Apr 2016 12:11:40 +0200	[thread overview]
Message-ID: <1828032.Xk8haRDBUM@xps13> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B43588FC5A3C@IRSMSX101.ger.corp.intel.com>

2016-04-05 09:48, Trahe, Fiona:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > 2016-04-05 08:53, Fiona Trahe:
> > > The cryptodev API was introduced in the DPDK 2.2 release.
> > > Since then it has
> > >  - been reviewed and iterated for the DPDK 16.04 release
> > >  - had extensive use by the l2fwd-crypto app,
> > > 			the ipsec-secgw example app,
> > > 			the test app.
> > > We believe it is now stable and the EXPERIMENTAL label should be removed.
> > 
> > Are you sure sure? :)
> > It means you will try hard to not change the API anymore or you'll need a
> > deprecation notice strongly agreed (outside of your team).
> 
> We're sure sure :)

I think we could change the namespace before making this API stable.
What about using a dpdk_ prefix instead of rte_ ?
(and some macros have CRYPTODEV or CDEV prefixes)

  reply	other threads:[~2016-04-05 10:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05  7:53 Fiona Trahe
2016-04-05  8:47 ` Thomas Monjalon
2016-04-05  9:48   ` Trahe, Fiona
2016-04-05 10:11     ` Thomas Monjalon [this message]
2016-04-05 13:29       ` [dpdk-dev] Change new libraries to have dpdk_ prefix instead of rte_ Declan Doherty
2016-04-05 14:03         ` Ananyev, Konstantin
2016-04-05 14:22           ` Thomas Monjalon
2016-04-05 16:45           ` Wiles, Keith
2016-04-06 11:05 ` [dpdk-dev] [PATCH] cryptodev: Remove EXPERIMENTAL label Fiona Trahe
2016-04-06 16:37   ` Thomas Monjalon
2016-04-06 16:46     ` Trahe, Fiona
2016-04-06 16:49       ` Thomas Monjalon
2016-04-06 17:07     ` 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=1828032.Xk8haRDBUM@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@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).