From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v4] pmd/snow3g: add new SNOW 3G SW PMD
Date: Thu, 10 Mar 2016 23:56:07 +0100 [thread overview]
Message-ID: <2802937.l2eUnEgDO1@xps13> (raw)
In-Reply-To: <1457627592-29144-1-git-send-email-pablo.de.lara.guarch@intel.com>
2016-03-10 16:33, Pablo de Lara:
> +SNOW 3G PMD
> +M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> +F: drivers/crypto/snow3g
Missing doc reference:
F: doc/guides/cryptodevs/snow3g.rst
> +To build DPDK with the SNOW3G_PMD the user is required to get
> +the export controlled libsso library, sending a request to
> +`DPDKUser_software_access@intel.com`, and compile it
> +on their user system before building DPDK:
I'm a bit concerned that this library is not freely available.
It makes testing difficult.
> +The environmental variable LIBSSO_PATH must be exported with the path
> +where you extracted and built the libsso library and finally set
> +CONFIG_RTE_LIBRTE_SNOW3G=y in config/common_base.
It is CONFIG_RTE_LIBRTE_PMD_SNOW3G.
> +# SNOW3G PMD is dependent on the LIBSSO library
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_SNOW3G) += -lrte_pmd_snow3g
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_SNOW3G) += -L$(LIBSSO_PATH)/build -lsso
> +
> endif # ! $(CONFIG_RTE_BUILD_SHARED_LIB)
This is for the static library case.
The PMD should be linked to libsso also in the shared library case.
There is the same problem with -lIPSec_MB (aesni_mb driver).
next prev parent reply other threads:[~2016-03-10 22:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 14:15 [PATCH] pmd/snow3g: add new SNOW 3G SW PMD Pablo de Lara
2016-03-07 14:07 ` [PATCH v2] " Pablo de Lara
2016-03-07 19:48 ` [PATCH v3] " Pablo de Lara
2016-03-08 14:10 ` Jain, Deepak K
2016-03-10 16:33 ` [PATCH v4] " Pablo de Lara
2016-03-10 16:54 ` Jain, Deepak K
2016-03-10 23:00 ` Thomas Monjalon
2016-03-10 22:56 ` Thomas Monjalon [this message]
2016-03-07 19:48 ` [PATCH v2] " De Lara Guarch, Pablo
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=2802937.l2eUnEgDO1@xps13 \
--to=thomas.monjalon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.