From: Radu Nicolau <radu.nicolau@intel.com>
To: dev@dpdk.org
Cc: Radu Nicolau <radu.nicolau@intel.com>
Subject: [PATCH 0/4] crypto/ipsec_mb: add support for IPsecMB 3.0
Date: Fri, 2 Oct 2026 09:56:20 +0000 [thread overview]
Message-ID: <20261002095652.1540556-1-radu.nicolau@intel.com> (raw)
Intel(R) Multi-Buffer Crypto for IPsec Library released version 3.0.0
codenamed Túnel Pablo
https://github.com/intel/intel-ipsec-mb/releases/tag/v3.0.0
This patchset adds support for the new library version and support
for the new algorithms included in this release.
Radu Nicolau (4):
crypto/ipsec_mb: add support for IPsecMB 3.0
crypto/ipsec_mb: add support for 256-NxA4/5/6 algorithms
crypto/ipsec_mb: add support for ML-KEM and ML-DSA
test/crypto: add asym test suite for AESNI_MB
app/test/test_cryptodev_asym.c | 7 +
doc/guides/cryptodevs/aesni_gcm.rst | 4 +-
doc/guides/cryptodevs/aesni_mb.rst | 26 +-
doc/guides/cryptodevs/features/aesni_mb.ini | 12 +
doc/guides/rel_notes/release_26_11.rst | 12 +
drivers/crypto/ipsec_mb/ipsec_mb_ops.c | 58 ++
drivers/crypto/ipsec_mb/ipsec_mb_private.h | 20 +
drivers/crypto/ipsec_mb/pmd_aesni_gcm.c | 267 +++++--
drivers/crypto/ipsec_mb/pmd_aesni_gcm_priv.h | 31 +-
drivers/crypto/ipsec_mb/pmd_aesni_mb.c | 695 +++++++++++++++++--
drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h | 360 +++++++++-
11 files changed, 1354 insertions(+), 138 deletions(-)
--
2.52.0
next reply other threads:[~2026-10-02 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 9:56 Radu Nicolau [this message]
2026-10-02 9:56 ` [PATCH 1/4] crypto/ipsec_mb: add support for IPsecMB 3.0 Radu Nicolau
2026-10-06 12:06 ` Ji, Kai
2026-10-02 9:56 ` [PATCH 2/4] crypto/ipsec_mb: add support for 256-NxA4/5/6 algorithms Radu Nicolau
2026-10-02 9:56 ` [PATCH 3/4] crypto/ipsec_mb: add support for ML-KEM and ML-DSA Radu Nicolau
2026-10-02 9:56 ` [PATCH 4/4] test/crypto: add asym test suite for AESNI_MB Radu Nicolau
2026-10-06 13:08 ` [PATCH 0/4] crypto/ipsec_mb: add support for IPsecMB 3.0 Ji, Kai
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=20261002095652.1540556-1-radu.nicolau@intel.com \
--to=radu.nicolau@intel.com \
--cc=dev@dpdk.org \
/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