DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@mellanox.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] Use Intel IPSec MB library in Wireless	PMDs
Date: Mon, 13 Jan 2020 14:17:44 +0000	[thread overview]
Message-ID: <AM0PR05MB44014151B2AB14BC47874B10D7350@AM0PR05MB4401.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1578915625-237451-1-git-send-email-pablo.de.lara.guarch@intel.com>

Hi,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Pablo de Lara
> Sent: Monday, January 13, 2020 1:40 PM
> To: akhil.goyal@nxp.com; declan.doherty@intel.com
> Cc: dev@dpdk.org; Pablo de Lara <pablo.de.lara.guarch@intel.com>
> Subject: [dpdk-dev] [PATCH v2 0/3] Use Intel IPSec MB library in Wireless
> PMDs
> 
> The three Intel SW Crypto PMDs supporting SNOW3G, ZUC and KASUMI link
> against libSSO libraries.
> The Intel IPSec Multi-buffer library recently integrated the code from these
> libraries, in version v0.53.
> This library can be downloaded from
<removed>
> 
> KASUMI, SNOW3G and ZUC PMDs have been modified to use this single
> library, which is already used in the AESNI MB and AESNI GCM PMDs,
> reducing the number of external dependencies in the crypto PMDs.
> 
> Changes in v2:
> - Updated ZUC PMD to support future AVX512 and AVX2 implementations.
> 
> Pablo de Lara (3):
>   crypto/zuc: use IPSec library
>   crypto/kasumi: use IPSec library
>   crypto/snow3g: use IPSec library
> 
>  devtools/test-build.sh                     | 16 ++----
>  doc/guides/cryptodevs/kasumi.rst           | 62 ++++++++++++----------
>  doc/guides/cryptodevs/snow3g.rst           | 58 +++++++++++---------
>  doc/guides/cryptodevs/zuc.rst              | 52 ++++++++++--------
>  doc/guides/rel_notes/release_20_02.rst     | 17 ++++++
>  drivers/crypto/kasumi/Makefile             | 26 +++++----
>  drivers/crypto/kasumi/kasumi_pmd_private.h | 12 +++--
>  drivers/crypto/kasumi/meson.build          | 24 ++++++---
>  drivers/crypto/kasumi/rte_kasumi_pmd.c     | 79 +++++++++++++++---------
> ---
>  drivers/crypto/kasumi/rte_kasumi_pmd_ops.c |  8 ++-
>  drivers/crypto/snow3g/Makefile             | 29 ++++++----
>  drivers/crypto/snow3g/meson.build          | 21 ++++++--
>  drivers/crypto/snow3g/rte_snow3g_pmd.c     | 85 ++++++++++++++++++---
> ---------
>  drivers/crypto/snow3g/rte_snow3g_pmd_ops.c |  8 ++-
> drivers/crypto/snow3g/snow3g_pmd_private.h | 14 +++--
>  drivers/crypto/zuc/Makefile                | 28 ++++++----
>  drivers/crypto/zuc/meson.build             | 24 ++++++---
>  drivers/crypto/zuc/rte_zuc_pmd.c           | 51 +++++++++++++-----
>  drivers/crypto/zuc/rte_zuc_pmd_ops.c       |  2 +
>  drivers/crypto/zuc/zuc_pmd_private.h       |  6 ++-
>  mk/rte.app.mk                              |  6 +--
>  21 files changed, 395 insertions(+), 233 deletions(-)
> 
> --
> 2.7.5

I see the following build failure when applying the patchset:
"""
../../root/dpdk/drivers/crypto/zuc/rte_zuc_pmd.c:225:51: error: cast from 'uint8_t **' (aka 'unsigned char **') to 'const void **' must have all intermediate pointers const qualified to be safe [-Werror,-Wcast-qual]
        IMB_ZUC_EEA3_N_BUFFER(qp->mb_mgr, (const void **)cipher_keys,
                                                         ^
../../root/dpdk/drivers/crypto/zuc/rte_zuc_pmd.c:226:19: error: cast from 'uint8_t **' (aka 'unsigned char **') to 'const void **' must have all intermediate pointers const qualified to be safe [-Werror,-Wcast-qual]
                        (const void **)iv, (const void **)src, (void **)dst,
                                       ^
../../root/dpdk/drivers/crypto/zuc/rte_zuc_pmd.c:226:38: error: cast from 'uint8_t **' (aka 'unsigned char **') to 'const void **' must have all intermediate pointers const qualified to be safe [-Werror,-Wcast-qual]
                        (const void **)iv, (const void **)src, (void **)dst,
                                                          ^
3 errors generated.
"""

It reproduces with meson on Fedora 31 and clang (version 9.0.0).
I'm using intel-ipsec-mb version 0.53.

Regards,
Ali

  parent reply	other threads:[~2020-01-13 14:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 14:20 [dpdk-dev] [PATCH " Pablo de Lara
2019-12-11 14:20 ` [dpdk-dev] [PATCH 1/3] crypto/zuc: use IPSec library Pablo de Lara
2019-12-11 14:20 ` [dpdk-dev] [PATCH 2/3] crypto/kasumi: " Pablo de Lara
2019-12-11 14:20 ` [dpdk-dev] [PATCH 3/3] crypto/snow3g: " Pablo de Lara
2020-01-13 11:40 ` [dpdk-dev] [PATCH v2 0/3] Use Intel IPSec MB library in Wireless PMDs Pablo de Lara
2020-01-13 11:40   ` [dpdk-dev] [PATCH v2 1/3] crypto/zuc: use IPSec library Pablo de Lara
2020-01-13 12:45     ` Bruce Richardson
2020-01-13 12:46       ` Bruce Richardson
2020-01-13 11:40   ` [dpdk-dev] [PATCH v2 2/3] crypto/kasumi: " Pablo de Lara
2020-01-13 11:40   ` [dpdk-dev] [PATCH v2 3/3] crypto/snow3g: " Pablo de Lara
2020-01-13 14:17   ` Ali Alnubani [this message]
2020-01-16  8:36     ` [dpdk-dev] [PATCH v2 0/3] Use Intel IPSec MB library in Wireless PMDs De Lara Guarch, Pablo
2020-01-16 11:41   ` [dpdk-dev] [PATCH v3 " Pablo de Lara
2020-01-16 11:41     ` [dpdk-dev] [PATCH v3 1/3] crypto/zuc: use IPSec library Pablo de Lara
2020-01-16 11:41     ` [dpdk-dev] [PATCH v3 2/3] crypto/kasumi: " Pablo de Lara
2020-01-16 11:41     ` [dpdk-dev] [PATCH v3 3/3] crypto/snow3g: " Pablo de Lara
2020-01-20 11:47     ` [dpdk-dev] [PATCH v4 0/3] Use Intel IPSec MB library in Wireless PMDs Pablo de Lara
2020-01-20 11:47       ` [dpdk-dev] [PATCH v4 1/3] crypto/zuc: use IPSec library Pablo de Lara
2020-01-20 11:47       ` [dpdk-dev] [PATCH v4 2/3] crypto/kasumi: " Pablo de Lara
2020-01-20 11:47       ` [dpdk-dev] [PATCH v4 3/3] crypto/snow3g: " Pablo de Lara
2020-01-21 10:22       ` [dpdk-dev] [PATCH v4 0/3] Use Intel IPSec MB library in Wireless PMDs 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=AM0PR05MB44014151B2AB14BC47874B10D7350@AM0PR05MB4401.eurprd05.prod.outlook.com \
    --to=alialnu@mellanox.com \
    --cc=akhil.goyal@nxp.com \
    --cc=declan.doherty@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).