From: Akhil Goyal <gakhil@marvell.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Wang, Yipeng1" <yipeng1.wang@intel.com>,
"Gobriel, Sameh" <sameh.gobriel@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
"nd@arm.com" <nd@arm.com>
Subject: RE: [PATCH 0/2] IPsec on Arm
Date: Fri, 26 Aug 2022 08:47:12 +0000 [thread overview]
Message-ID: <CO6PR18MB44849501EF741A89F2C4A82BD8759@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <MW5PR11MB5809702A037F6520300136D4B8719@MW5PR11MB5809.namprd11.prod.outlook.com>
> Hi Ruifeng,
>
> We have no technical issues with these patches based on their current
> functionality. However, it is worth pointing out that we are planning some
> changes to the Intel(r) Multi-Buffer Crypto for IPSec library which will require API
> changes in the future. These changes are, but not limited to, to consolidate
> some of the crypto PMDs into a single PMD, which will simplify the code and
> reduce future maintenance effort. When these changes are made, your library
> will need to be updated too in order to take advantage of the consolidation. We
> can provide further details of the changes that we're considering separately, so
> that you're not taken by surprise when these change occurs.
>
> We also want you to know, for any change we will make to these PMDs, we do
> not guarantee it works on ARM platform. We advise you to do necessary
> testing/verification in necessary testing/verification to the future patches for
> the PMDs based on ipsec-mb on your platform.
> > This patch set integrates Arm port of ipsec_mb library.
> > ZUC and SNOW3g PMDs are available on Arm platform with this integration.
> >
> > This series depends on:
> > https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__patches.dpdk.org_project_dpdk_patch_20220630154123.2565439-2D1-
> 2D&d=DwIF-
> g&c=nKjWec2b6R0mOyPaz7xtfQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPw
> uqhd6WNyo&m=MSflaO84SEZbIx1iRuPLHdFCx1Tt55MDafiMzZITc2CEoY-
> Zid36my-fIfMSmooi&s=rLK324Pjv9lI3_LVXCQaQ6-Yb7fT9y1kE6_S68741Ec&e=
> > asekhar@marvell.com/
> >
> > Depends-on: patch-113578 ("crypto/ipsec_mb: enable support for arm64")
> >
> > Ruifeng Wang (2):
> > crypto/ipsec_mb: remove redundant includes
> > crypto/ipsec_mb: enable IPsec on Arm platform
> >
> > app/test/test_cryptodev_hash_test_vectors.h | 4 ++++
> > doc/guides/cryptodevs/snow3g.rst | 14 ++++++++++----
> > doc/guides/cryptodevs/zuc.rst | 14 ++++++++++----
> > drivers/common/qat/meson.build | 6 +++++-
> > drivers/crypto/ipsec_mb/ipsec_mb_private.c | 6 ++++++
> > drivers/crypto/ipsec_mb/ipsec_mb_private.h | 4 ++++
> > drivers/crypto/ipsec_mb/meson.build | 6 +++++-
> > drivers/crypto/ipsec_mb/pmd_aesni_gcm_priv.h | 2 --
> > drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h | 2 --
> > drivers/crypto/qat/qat_sym_session.c | 4 ++++
> > 10 files changed, 48 insertions(+), 14 deletions(-)
Series applied to dpdk-next-crypto
Thanks
prev parent reply other threads:[~2022-08-26 8:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 8:13 Ruifeng Wang
2022-07-27 8:13 ` [PATCH 1/2] crypto/ipsec_mb: remove redundant includes Ruifeng Wang
2022-07-27 8:13 ` [PATCH 2/2] crypto/ipsec_mb: enable IPsec on Arm platform Ruifeng Wang
2022-07-27 8:34 ` David Marchand
2022-07-27 8:42 ` Ruifeng Wang
2022-07-27 17:42 ` Honnappa Nagarahalli
2022-07-27 8:50 ` Ashwin Sekhar T K
2022-08-16 15:57 ` [EXT] [PATCH 0/2] IPsec on Arm Akhil Goyal
2022-08-22 7:54 ` Zhang, Roy Fan
2022-08-22 8:38 ` Ruifeng Wang
2022-08-26 8:47 ` 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=CO6PR18MB44849501EF741A89F2C4A82BD8759@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=nd@arm.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=sameh.gobriel@intel.com \
--cc=vladimir.medvedkin@intel.com \
--cc=yipeng1.wang@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).