DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: akhil.goyal@nxp.com, declan.doherty@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 1/3] crypto/zuc: use IPSec library
Date: Mon, 13 Jan 2020 12:45:14 +0000	[thread overview]
Message-ID: <20200113124514.GA1645@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <1578915625-237451-2-git-send-email-pablo.de.lara.guarch@intel.com>

On Mon, Jan 13, 2020 at 11:40:23AM +0000, Pablo de Lara wrote:
> Link against Intel IPSec Multi-buffer library, which
> added support for ZUC-EEA3 and ZUC-EIA3 from version v0.53,
> moving from libSSO ZUC library.
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
>  devtools/test-build.sh                 |  6 ++--
>  doc/guides/cryptodevs/zuc.rst          | 52 ++++++++++++++++++++--------------
>  doc/guides/rel_notes/release_20_02.rst |  7 +++++
>  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                          |  2 +-
>  9 files changed, 120 insertions(+), 58 deletions(-)
> 

<snip>

> diff --git a/drivers/crypto/zuc/meson.build b/drivers/crypto/zuc/meson.build
> index b231de0..b7098a3 100644
> --- a/drivers/crypto/zuc/meson.build
> +++ b/drivers/crypto/zuc/meson.build
> @@ -1,14 +1,26 @@
>  # SPDX-License-Identifier: BSD-3-Clause
> -# Copyright(c) 2018 Intel Corporation
> +# Copyright(c) 2018-2019 Intel Corporation
>  
> -lib = cc.find_library('sso_zuc', required: false)
> -if not lib.found() or not cc.has_header('sso_zuc.h')
> +IMB_required_ver = '0.53.0'
> +lib = cc.find_library('IPSec_MB', required: false)
> +if not lib.found()
>  	build = false
> -	reason = 'missing dependency, "libsso_zuc"'
> -	subdir_done()
> +	reason = 'missing dependency, "libIPSec_MB"'
> +else
> +	ext_deps += lib
> +
> +	# version comes with quotes, so we split based on " and take the middle
> +	imb_ver = cc.get_define('IMB_VERSION_STR',
> +		prefix : '#include<intel-ipsec-mb.h>').split('"')[1]
> +
> +	if (imb_ver == '') or (imb_ver.version_compare('<' + IMB_required_ver))
> +		message('IPSec_MB version >= @0@ is required, found version @1@'.format(
> +				IMB_required_ver, imb_ver))
> +		build = false

Rather than/As well as printing a message here, you also need to provide a
reason when setting build = false, so the summary at the end can report why
the driver is not being built.

> +	endif
> +
>  endif
>  
>  allow_experimental_apis = true
> -ext_deps += lib

If you drop the line after the else above, you can keep this line and
shrink the diff by 2 lines. :-)

/Bruce

  reply	other threads:[~2020-01-13 12:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 14:20 [dpdk-dev] [PATCH 0/3] Use Intel IPSec MB library in Wireless PMDs 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 [this message]
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   ` [dpdk-dev] [PATCH v2 0/3] Use Intel IPSec MB library in Wireless PMDs Ali Alnubani
2020-01-16  8:36     ` 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=20200113124514.GA1645@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.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).