From: Akhil Goyal <akhil.goyal@nxp.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 0/3] Use Intel IPSec MB library in Wireless PMDs
Date: Tue, 21 Jan 2020 10:22:56 +0000 [thread overview]
Message-ID: <VE1PR04MB66398EB514D58189E1BE4686E60D0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1579520876-221343-1-git-send-email-pablo.de.lara.guarch@intel.com>
> 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
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
> m%2Fintel%2Fintel-ipsec-
> mb&data=02%7C01%7Cakhil.goyal%40nxp.com%7C5ffd94496dc54ff2320a
> 08d79d9e9c28%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637151
> 176851109882&sdata=FtTqorVaqtV89FBjDasUeK5lq%2B0Z8jj42iGzoIyVOG
> w%3D&reserved=0.
>
> 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 v4:
> - Rebased against latest dpdk-next-crypto
>
Series
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2020-01-21 10:23 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 ` [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 ` Akhil Goyal [this message]
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=VE1PR04MB66398EB514D58189E1BE4686E60D0@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=bruce.richardson@intel.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).