DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Radu Nicolau <radu.nicolau@intel.com>
To: Wathsala Vithanage <wathsala.vithanage@arm.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Ji, Kai" <kai.ji@intel.com>,
	Akhil Goyal <gakhil@marvell.com>,
	David Marchand <david.marchand@redhat.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Jack Bond-Preston <jack.bond-preston@foss.arm.com>,
	Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	Paul Szczepanek <paul.szczepanek@arm.com>,
	<jyotsna.chitri@arm.com>
Subject: Re: [PATCH v2] crypto/ipsec_mb: require minimum version 2.0 for IPsec MB
Date: Wed, 21 Oct 2026 09:27:35 +0100	[thread overview]
Message-ID: <6cdc2640-9eab-42c3-9b45-c06365fb0b92@intel.com> (raw)
In-Reply-To: <68a2da9f-81c6-451e-806f-ddfbfcd67361@arm.com>


On 15-Oct-26 4:46 PM, Wathsala Vithanage wrote:
>
> On 10/14/26 09:42, Thomas Monjalon wrote:
>> 14/10/2026 14:44, Radu Nicolau:
>>> On 14-Oct-26 1:16 PM, Thomas Monjalon wrote:
>>>> 14/10/2026 11:37, Radu Nicolau:
>>>>> On 13-Oct-26 8:51 PM, Thomas Monjalon wrote:
>>>>>> 24/09/2026 13:18, Akhil Goyal:
>>>>>>>> From: Nicolau, Radu <radu.nicolau@intel.com>
>>>>>>>>> Increase the minimum required IPsec MB library version to 2.0 
>>>>>>>>> As a
>>>>>>>>> consequence, clean up the aesni_mb PMD code.
>>>>>>>>>
>>>>>>>>> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
>>>>>>>> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>>>>>>> Applied to dpdk-next-crypto
>>>>>> As usual with Intel IPsec MB, it triggers a compilation failure 
>>>>>> on Arm:
>>>>>>
>>>>>> drivers/crypto/ipsec_mb/pmd_aesni_mb.c:24:32:
>>>>>> error: 'IMB_CIPHER_SM4_GCM' undeclared
>>>>>>
>>>>>> I have to drop this commit while pulling next-crypto in main.
>>>>>>
>>>>>> Please find a solution.
>>>>>> I'm still advocating to merge the Arm fork.
>>>>> Hi Thomas, the root cause of the build failure on Arm is their 
>>>>> library
>>>>> fork which lags behind, being at 1.5 release which is at this point
>>>>> almost 3 years old.
>>>>>
>>>>> The only solution in this release cycle is to drop this patch and 
>>>>> rebase
>>>>> the ones adding support for 3.0.
>>>>>
>>>>> Considering Arm lack of support and contributions for these PMD 
>>>>> over the
>>>>> last couple of years, the only long term solution I see to avoid PMD
>>>>> code littered with ifdefs and supporting very old releases of the
>>>>> library is to drop the Arm version altogether.
>>>> No.
>>>> The only solution is to work with Arm.
>>> Indeed that would be the ideal solution.
>>>
>>> If anyone @Arm is still watching this space, please chip in.
>> Adding Arm folks
>
> Hi Thomas,
> We are looking into the  build issue and how best to resolve it.
> Also, would be happy to start a conversation on how we could work on a 
> combined fork.
>
> --wathsala

Hi Wathsala, can you have a look at the latest patches and ack them if 
all ok? The Arm compilation issue was resolved by removing the patch for 
minimum version, and all patches were rebased.

https://patches.dpdk.org/project/dpdk/list/?series=39660

Thanks,
Radu

      reply	other threads:[~2026-10-21  8:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 11:26 [PATCH] crypto/ipsec_mb: require minimum version 2.0 for IPsec MB Radu Nicolau
2026-08-11 15:53 ` Stephen Hemminger
2026-08-11 16:21   ` Radu Nicolau
2026-08-17  9:39 ` [PATCH v2] " Radu Nicolau
2026-08-17 12:06   ` De Lara Guarch, Pablo
2026-09-24 11:18     ` Akhil Goyal
2026-10-13 19:51       ` Thomas Monjalon
2026-10-14  9:37         ` Radu Nicolau
2026-10-14 12:16           ` Thomas Monjalon
2026-10-14 12:44             ` Radu Nicolau
2026-10-14 14:05               ` [EXTERNAL] " Akhil Goyal
2026-10-14 14:42               ` Thomas Monjalon
2026-10-15 15:46                 ` Wathsala Vithanage
2026-10-21  8:27                   ` Radu Nicolau [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=6cdc2640-9eab-42c3-9b45-c06365fb0b92@intel.com \
    --to=radu.nicolau@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jack.bond-preston@foss.arm.com \
    --cc=john.mcnamara@intel.com \
    --cc=jyotsna.chitri@arm.com \
    --cc=kai.ji@intel.com \
    --cc=paul.szczepanek@arm.com \
    --cc=thomas@monjalon.net \
    --cc=wathsala.vithanage@arm.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