From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add cryptodev xform deprecation notice
Date: Thu, 28 Feb 2019 11:27:49 +0000 [thread overview]
Message-ID: <9F7182E3F746AB4EA17801C148F3C60433587C1E@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <e95d2fad-10b7-d453-756e-32bce2a86904@nxp.com>
Hi,
The reason of this change is for a more formal API for cryptodev. Since the
key is for creating session and not meant to be modified by the driver.
The patch is finished I am doing some last checks. Is there any reason to
delay the patch for 19.08?
Regards,
Fan
> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Thursday, February 28, 2019 10:08 AM
> To: Zhang, Roy Fan <roy.fan.zhang@intel.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: add cryptodev xform deprecation
> notice
>
> Hi Fan,
>
> On 2/8/2019 4:47 PM, Fan Zhang wrote:
> > This patch adds the deprecation notice of changing Cryptodev symmetric
> > xform structure for DPDK 19.05.
> It would be better if a need of this change is explained in the description of
> the patch and I believe the change will be accepted for
> 19.08 release and not 19.05.
> >
> > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> > ---
> > doc/guides/rel_notes/deprecation.rst | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/deprecation.rst
> > b/doc/guides/rel_notes/deprecation.rst
> > index 1b4fcb7e6..5166d6eb5 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -75,3 +75,9 @@ Deprecation Notices
> >
> > * crypto/aesni_mb: the minimum supported intel-ipsec-mb library version
> will be
> > changed from 0.49.0 to 0.52.0.
> > +
> > +* cryptodev: the ``uint8_t *data`` member of ``key`` structure in the
> > +xforms
> > + structure (``rte_crypto_cipher_xform``, ``rte_crypto_auth_xform``,
> > +and
> > + ``rte_crypto_aead_xform``) will be changed to ``const uint8_t
> > +*data`` in
> > + 19.05. The structure ``rte_table_action_sym_crypto_params`` in
> > +pipeline
> > + library will be updated accordingly.
next prev parent reply other threads:[~2019-02-28 11:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 11:17 Fan Zhang
2019-02-28 10:08 ` Akhil Goyal
2019-02-28 11:27 ` Zhang, Roy Fan [this message]
2019-03-01 10:46 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2019-03-22 16:34 ` [dpdk-dev] [PATCH v3] " Fan Zhang
2019-03-22 16:34 ` Fan Zhang
2019-03-29 13:59 ` Akhil Goyal
2019-03-29 13:59 ` Akhil Goyal
2019-03-29 14:15 ` Akhil Goyal
2019-03-29 14:15 ` Akhil Goyal
2019-03-29 15:49 ` Akhil Goyal
2019-03-29 15:49 ` Akhil Goyal
2019-03-29 15:59 ` Akhil Goyal
2019-03-29 15:59 ` Akhil Goyal
2019-03-29 19:56 ` Thomas Monjalon
2019-03-29 19:56 ` Thomas Monjalon
2019-04-01 16:29 ` Trahe, Fiona
2019-04-01 16:29 ` Trahe, Fiona
2019-04-03 9:11 ` Anoob Joseph
2019-04-03 9:11 ` Anoob Joseph
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=9F7182E3F746AB4EA17801C148F3C60433587C1E@IRSMSX101.ger.corp.intel.com \
--to=roy.fan.zhang@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).