All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.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>,
	"gakhil@marvell.com" <gakhil@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	nd <nd@arm.com>, nd <nd@arm.com>
Subject: RE: [PATCH 0/2] IPsec on Arm
Date: Mon, 22 Aug 2022 08:38:24 +0000	[thread overview]
Message-ID: <AS8PR08MB7080B7C20771B07B2B99A55E9E719@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <MW5PR11MB5809702A037F6520300136D4B8719@MW5PR11MB5809.namprd11.prod.outlook.com>

> -----Original Message-----
> From: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Sent: Monday, August 22, 2022 3:54 PM
> To: 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>; gakhil@marvell.com
> Cc: dev@dpdk.org; Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; nd <nd@arm.com>
> Subject: RE: [PATCH 0/2] IPsec on Arm
> 
> Hi Ruifeng,
Hi Fan,

> 
> 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
Thanks for the heads-up. Really appreciate it.

> 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.
Yep, let's communicate this in a separate thread.

> 
> 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.
Yes, I will verify ZUC/SNOW3g PMD patches on Arm platform.

> 
> Regards,
> Fan
> 
> > -----Original Message-----
> > From: Ruifeng Wang <ruifeng.wang@arm.com>
> > Sent: Wednesday, July 27, 2022 9:14 AM
> > To: Zhang, Roy Fan <roy.fan.zhang@intel.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>; gakhil@marvell.com
> > Cc: dev@dpdk.org; honnappa.nagarahalli@arm.com; nd@arm.com; Ruifeng
> > Wang <ruifeng.wang@arm.com>
> > Subject: [PATCH 0/2] IPsec on Arm
> >
> > 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:
> > http://patches.dpdk.org/project/dpdk/patch/20220630154123.2565439-1-
> > 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(-)
> >
> > --
> > 2.25.1


  reply	other threads:[~2022-08-22  8:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27  8:13 [PATCH 0/2] IPsec on Arm 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 [this message]
2022-08-26  8:47   ` 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=AS8PR08MB7080B7C20771B07B2B99A55E9E719@AS8PR08MB7080.eurprd08.prod.outlook.com \
    --to=ruifeng.wang@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=nd@arm.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=roy.fan.zhang@intel.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 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.