DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add cryptodev gcm iv deprecation notice
Date: Wed, 17 Apr 2019 11:32:01 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B43589743C1B@IRSMSX101.ger.corp.intel.com> (raw)
Message-ID: <20190417113201.GShrhcWg9MThHZiePs2KYI3x8KwMX12yo-zUvK7bWJg@z> (raw)
In-Reply-To: <20190417074113.10896-1-arkadiuszx.kusztal@intel.com>



> -----Original Message-----
> From: Kusztal, ArkadiuszX
> Sent: Wednesday, April 17, 2019 8:41 AM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Trahe, Fiona <fiona.trahe@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH] doc: add cryptodev gcm iv deprecation notice
> 
> 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.
[Fiona] nit - I would say "With this change..." rather than "Right now..."
Apart from this
Acked-by: Fiona Trahe <fiona.trahe@intel.com>


> 
> 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-04-17 11:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17  7:41 Arek Kusztal
2019-04-17  7:41 ` Arek Kusztal
2019-04-17 11:32 ` Trahe, Fiona [this message]
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
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
2019-05-04 18:06     ` Liron Himi

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=348A99DA5F5B7549AA880327E580B43589743C1B@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@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).