DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wathsala Vithanage <wathsala.vithanage@arm.com>
To: Kai Ji <kai.ji@intel.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, nd@arm.com, Paul.Elliott@arm.com,
	Dhruv.Tripathi@arm.com, Shebu.VargheseKuriakose@arm.com,
	Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: [PATCH 1/2] crypto/ipsec_mb: allow aesni_mb and aesni_gcm vdevs on Arm
Date: Fri, 29 May 2026 20:55:11 +0000	[thread overview]
Message-ID: <20260529205512.1985844-1-wathsala.vithanage@arm.com> (raw)

Extend Arm PMD gating in ipsec_mb_create() to permit
IPSEC_MB_PMD_TYPE_AESNI_MB and IPSEC_MB_PMD_TYPE_AESNI_GCM
in addition to existing SNOW3G and ZUC.

This removes -ENOTSUP rejection for crypto_aesni_mb and
crypto_aesni_gcm on Arm, enabling these vdevs to probe and run
when backed by a compatible ipsec-mb library.

Signed-off-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
---
 drivers/crypto/ipsec_mb/ipsec_mb_private.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/crypto/ipsec_mb/ipsec_mb_private.c b/drivers/crypto/ipsec_mb/ipsec_mb_private.c
index b4c36e7f58..468d77fead 100644
--- a/drivers/crypto/ipsec_mb/ipsec_mb_private.c
+++ b/drivers/crypto/ipsec_mb/ipsec_mb_private.c
@@ -72,7 +72,9 @@ ipsec_mb_create(struct rte_vdev_device *vdev,
 
 #if defined(RTE_ARCH_ARM)
 	if ((pmd_type != IPSEC_MB_PMD_TYPE_SNOW3G) &&
-		(pmd_type != IPSEC_MB_PMD_TYPE_ZUC))
+		(pmd_type != IPSEC_MB_PMD_TYPE_ZUC) &&
+		(pmd_type != IPSEC_MB_PMD_TYPE_AESNI_MB) &&
+		(pmd_type != IPSEC_MB_PMD_TYPE_AESNI_GCM))
 		return -ENOTSUP;
 #endif
 
-- 
2.43.0


             reply	other threads:[~2026-05-29 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 20:55 Wathsala Vithanage [this message]
2026-05-29 21:04 ` [PATCH 2/2] doc: update Arm IPsec-MB references for cryptodev PMDs Wathsala Vithanage
2026-06-02 12:10   ` Hemant Agrawal
2026-06-02 12:09 ` [PATCH 1/2] crypto/ipsec_mb: allow aesni_mb and aesni_gcm vdevs on Arm Hemant Agrawal
2026-06-20 18:43   ` 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=20260529205512.1985844-1-wathsala.vithanage@arm.com \
    --to=wathsala.vithanage@arm.com \
    --cc=Dhruv.Tripathi@arm.com \
    --cc=Paul.Elliott@arm.com \
    --cc=Shebu.VargheseKuriakose@arm.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=nd@arm.com \
    --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