DPDK patches and discussions
 help / color / mirror / Atom feed
From: Liron Himi <lironh@marvell.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
	"Doherty, Declan" <declan.doherty@intel.com>,
	"ravi1.kumar@amd.com" <ravi1.kumar@amd.com>,
	"tdu@semihalf.com" <tdu@semihalf.com>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"Anoob Joseph" <anoobj@marvell.com>,
	Shally Verma <shallyv@marvell.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	Liron Himi <lironh@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add cryptodev gcm iv deprecation notice
Date: Sat, 4 May 2019 18:06:41 +0000	[thread overview]
Message-ID: <MN2PR18MB2398BA13E56A2FAAF7D6FC15C6360@MN2PR18MB2398.namprd18.prod.outlook.com> (raw)
Message-ID: <20190504180641.uBckk4ZS5KzUggU1qaypuDlkO-1CEcyFBKzFgUwVIU8@z> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B43589751F08@IRSMSX101.ger.corp.intel.com>

+1

Regards,
Liron

-----Original Message-----
From: Trahe, Fiona <fiona.trahe@intel.com> 
Sent: Friday, May 3, 2019 9:10 PM
To: Doherty, Declan <declan.doherty@intel.com>; ravi1.kumar@amd.com; tdu@semihalf.com; Liron Himi <lironh@marvell.com>; Alan Winkowski <walan@marvell.com>
Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; dev@dpdk.org; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; Anoob Joseph <anoobj@marvell.com>; Shally Verma <shallyv@marvell.com>; akhil.goyal@nxp.com; Trahe, Fiona <fiona.trahe@intel.com>
Subject: [EXT] RE: [PATCH] doc: add cryptodev gcm iv deprecation notice

External Email

----------------------------------------------------------------------
Forwarding to maintainers of the following crypto PMDs which may be affected by this:
mvsam
ccp
openssl
Can you review the 19.05 deprecation notice below and if in agreement, ack please - 3 acks are needed

This is the related API change targeted at 19.08:
https://patches.dpdk.org/patch/52886/


> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Tuesday, April 30, 2019 7:59 AM
> To: Anoob Joseph <anoobj@marvell.com>; shallyv@marvell.com
> Cc: Trahe, Fiona <fiona.trahe@intel.com>; De Lara Guarch, Pablo 
> <pablo.de.lara.guarch@intel.com>; dev@dpdk.org; Kusztal, ArkadiuszX 
> <arkadiuszx.kusztal@intel.com>
> Subject: RE: [PATCH] doc: add cryptodev gcm iv deprecation notice
> 
> Hi Anoob/Shally,
> 
> Could you please review this patch and provide Ack.
> 
> Thanks,
> Akhil
> 
> 
> >
> >
> > This patch adds deprecation notice of changing iv behaviour when 
> > using Galois Counter Mode of operation. Right now IV of all 
> > supported sizes can be used.
> >
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@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 ba39c2d..76eb166 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -87,3 +87,9 @@ Deprecation Notices
> >  * 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``.
> > +
> > +* cryptodev: support for using IV with all sizes is added, J0 still 
> > +can
> > +  be used but only when IV length in following structs 
> > +``rte_crypto_auth_xform``,
> > +  ``rte_crypto_aead_xform`` is set to zero. When IV length is 
> > +greater or equal
> > +  to one it means it represents IV, when is set to zero it means J0 
> > +is used
> > +  directly, in this case 16 bytes of J0 need to be passed.
> > --
> > 2.1.0


  parent reply	other threads:[~2019-05-04 18:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30  6:59 Akhil Goyal
2019-04-30  6:59 ` Akhil Goyal
2019-05-03 18:09 ` Trahe, Fiona
2019-05-03 18:09   ` Trahe, Fiona
2019-05-04 18:06   ` Liron Himi [this message]
2019-05-04 18:06     ` Liron Himi
  -- strict thread matches above, loose matches on Subject: below --
2019-04-17  7:41 Arek Kusztal
2019-04-17  7:41 ` Arek Kusztal
2019-04-17 11:32 ` Trahe, Fiona
2019-04-17 11:32   ` Trahe, Fiona
2019-05-13 21:25   ` Thomas Monjalon
2019-05-13 21:25     ` Thomas Monjalon
2019-05-08  8:23 ` De Lara Guarch, Pablo
2019-05-08  8:23   ` De Lara Guarch, Pablo
2019-05-09  9:03   ` Akhil Goyal
2019-05-09  9:03     ` Akhil Goyal
2019-05-09 11:31 ` Anoob Joseph
2019-05-09 11:31   ` 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=MN2PR18MB2398BA13E56A2FAAF7D6FC15C6360@MN2PR18MB2398.namprd18.prod.outlook.com \
    --to=lironh@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=ravi1.kumar@amd.com \
    --cc=shallyv@marvell.com \
    --cc=tdu@semihalf.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).