From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/aesni_mb: support newer version library only
Date: Wed, 20 Mar 2019 17:44:15 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8978039AF9D@irsmsx112.ger.corp.intel.com> (raw)
Message-ID: <20190320174415.4pLKmmS7AX1GDSna3FcS_WfZsU9HyD963syzIpy96dY@z> (raw)
In-Reply-To: <20190304145735.25267-1-roy.fan.zhang@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Fan Zhang
> Sent: Monday, March 4, 2019 2:58 PM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Zhang, Roy Fan <roy.fan.zhang@intel.com>; Trahe,
> Fiona <fiona.trahe@intel.com>
> Subject: [dpdk-dev] [PATCH v2] crypto/aesni_mb: support newer version
> library only
>
> As stated in 19.02 deprecation notice, this patch updates the
> aesni_mb PMD to remove the support of older Intel-ipsec-mb
> library version eariler than 0.52.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
>
> v2:
> - fixed incorrect version in documentation.
>
> doc/guides/cryptodevs/aesni_mb.rst | 8 +-
> doc/guides/rel_notes/deprecation.rst | 3 -
> drivers/crypto/aesni_mb/Makefile | 21 +-
> drivers/crypto/aesni_mb/aesni_mb_ops.h | 302 -----
> drivers/crypto/aesni_mb/meson.build | 13 +-
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd_compat.c | 1313 ------------------
> --
> .../crypto/aesni_mb/rte_aesni_mb_pmd_ops_compat.c | 745 -----------
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h | 37 -
> 8 files changed, 16 insertions(+), 2426 deletions(-)
> delete mode 100644 drivers/crypto/aesni_mb/aesni_mb_ops.h
> delete mode 100644 drivers/crypto/aesni_mb/rte_aesni_mb_pmd_compat.c
> delete mode 100644
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops_compat.c
>
> diff --git a/doc/guides/cryptodevs/aesni_mb.rst
> b/doc/guides/cryptodevs/aesni_mb.rst
> index 47f2ecc2f..66c44e03a 100644
> --- a/doc/guides/cryptodevs/aesni_mb.rst
> +++ b/doc/guides/cryptodevs/aesni_mb.rst
> @@ -57,10 +57,7 @@ Limitations
>
> * Chained mbufs are not supported.
> * Only in-place is currently supported (destination address is the same as
> source address).
> -* RTE_CRYPTO_AEAD_AES_GCM only works properly when the multi-buffer
> library is
> - 0.51.0 or newer.
> -* RTE_CRYPTO_HASH_AES_GMAC is supported by library version v0.51 or
> later.
> -* RTE_CRYPTO_HASH_SHA* is supported by library version v0.52 or later.
> +* Only support Intel multi buffer library version 0.52 or later.
>
I'd say it is not needed to state this as a limitation.
>
> Installation
> @@ -92,7 +89,8 @@ and the Multi-Buffer library version supported by them:
> 17.05 - 17.08 0.45 - 0.48
> 17.11 0.47 - 0.48
> 18.02 0.48
> - 18.05+ 0.49+
> + 18.05 0.49
Change to 18.05 - 19.02 0.49 - 0.52
> + 19.05+ 0.52+
> ============== ============================
>
>
Apart from this:
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2019-03-20 17:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 11:47 [dpdk-dev] [PATCH] " Fan Zhang
2019-03-04 14:47 ` Trahe, Fiona
2019-03-04 14:57 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2019-03-20 17:44 ` De Lara Guarch, Pablo [this message]
2019-03-20 17:44 ` De Lara Guarch, Pablo
2019-03-25 13:58 ` [dpdk-dev] [PATCH v3] " Fan Zhang
2019-03-25 13:58 ` Fan Zhang
2019-03-26 9:10 ` Akhil Goyal
2019-03-26 9:10 ` Akhil Goyal
2019-03-26 15:35 ` Zhang, Roy Fan
2019-03-26 15:35 ` Zhang, Roy Fan
2019-03-26 15:43 ` Akhil Goyal
2019-03-26 15:43 ` Akhil Goyal
2019-03-29 14:38 ` Akhil Goyal
2019-03-29 14:38 ` Akhil Goyal
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=E115CCD9D858EF4F90C690B0DCB4D8978039AF9D@irsmsx112.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=roy.fan.zhang@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).