From: David Marchand <david.marchand@redhat.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: Fan Zhang <roy.fan.zhang@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
"Wang, Yipeng1" <yipeng1.wang@intel.com>,
"Gobriel, Sameh" <sameh.gobriel@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Akhil Goyal <gakhil@marvell.com>, dev <dev@dpdk.org>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
nd <nd@arm.com>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH 2/2] crypto/ipsec_mb: enable IPsec on Arm platform
Date: Wed, 27 Jul 2022 10:34:23 +0200 [thread overview]
Message-ID: <CAJFAV8ymon_M_qfSvHC=FifAxYDOxOKOdwtkyO+Q=Amf0fDBOg@mail.gmail.com> (raw)
In-Reply-To: <20220727081352.1333695-3-ruifeng.wang@arm.com>
On Wed, Jul 27, 2022 at 10:14 AM Ruifeng Wang <ruifeng.wang@arm.com> wrote:
>
> Arm port of ipsec_mb library [1] has different header file name than
> the Intel ipsec_mb library. Proper header name is picked according to
> the architecture to get the code compile when ipsec_mb is installed on
> Arm platform.
>
> And the Arm port currently supports ZUC and SNOW3g. Call to other
> algorithms will be blocked.
>
> [1] https://gitlab.arm.com/arm-reference-solutions/ipsec-mb/-/tree/main
Is it planned to get this port merged in the original repo?
--
David Marchand
next prev parent reply other threads:[~2022-07-27 8:34 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 [this message]
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
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='CAJFAV8ymon_M_qfSvHC=FifAxYDOxOKOdwtkyO+Q=Amf0fDBOg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--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=thomas@monjalon.net \
--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).