From: "Doherty, Declan" <declan.doherty@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
dev@dpdk.org,
Pablo DeLara Guarch <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] crypto drivers in the API
Date: Tue, 14 Feb 2017 14:46:55 +0000 [thread overview]
Message-ID: <18f43aad-8ae8-3549-aabb-fa7618b1c36a@intel.com> (raw)
In-Reply-To: <1704265.GvoO55czvH@xps13>
On 14/02/2017 11:04 AM, Thomas Monjalon wrote:
> 2017-02-14 10:44, Doherty, Declan:
>> On 13/02/2017 1:25 PM, Thomas Monjalon wrote:
>>> In the crypto API, the drivers are listed.
>>> In my opinion, it is a wrong designed and these lists should be removed.
>>> Do we need a deprecation notice to plan this removal in 17.05, while
>>> working on bus abstraction?
>>>
>> ...
>>>
...
>
> Yes
> If you were planning to do this, you should have sent a deprecation notice
> few weeks ago.
> Please send it now and we'll see if we have enough supporters shortly.
>
Thomas, there are a couple of other changes we are looking at in the
cryptodev which would require API changes as well as break ABI including
adding support for a multi-device sessions, and changes to crypto
operation layout and field changes for performance but these but will
require RFCs or at least more discussion of the proposals. Given the
time constrains for the V1 deadline for 17.05 I would prefer to work on
the RFCs and get them out as soon as possible over the next few weeks
and then make all the ABI breaking changes in R17.08 in a single release.
Otherwise we will end up breaking ABI 2 release in a row which I would
like to avoid if possible.
next prev parent reply other threads:[~2017-02-14 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 13:25 Thomas Monjalon
2017-02-13 13:29 ` Thomas Monjalon
2017-02-14 10:44 ` Doherty, Declan
2017-02-14 11:04 ` Thomas Monjalon
2017-02-14 14:46 ` Doherty, Declan [this message]
2017-02-14 15:47 ` 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=18f43aad-8ae8-3549-aabb-fa7618b1c36a@intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas.monjalon@6wind.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).