From: Emma Finn <emma.finn@intel.com>
To: Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, Emma Finn <emma.finn@intel.com>
Subject: [PATCH 2/2] crypto/ipsec_mb: Add SHAKE support.
Date: Mon, 5 Oct 2026 12:30:40 +0000 [thread overview]
Message-ID: <20261005123041.429121-2-emma.finn@intel.com> (raw)
In-Reply-To: <20261005123041.429121-1-emma.finn@intel.com>
Add SHAKE-128 and SHAKE-256 support to
ipsec_mb PMD.
Signed-off-by: Emma Finn <emma.finn@intel.com>
---
doc/guides/cryptodevs/aesni_mb.rst | 2 +
doc/guides/cryptodevs/features/aesni_mb.ini | 2 +
doc/guides/rel_notes/release_26_11.rst | 1 +
drivers/crypto/ipsec_mb/pmd_aesni_mb.c | 8 +++
drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h | 54 +++++++++++++++++++--
5 files changed, 64 insertions(+), 3 deletions(-)
diff --git a/doc/guides/cryptodevs/aesni_mb.rst b/doc/guides/cryptodevs/aesni_mb.rst
index 663b9f19d4b..da37d54471e 100644
--- a/doc/guides/cryptodevs/aesni_mb.rst
+++ b/doc/guides/cryptodevs/aesni_mb.rst
@@ -69,6 +69,8 @@ Hash algorithms:
* RTE_CRYPTO_AUTH_SHA3_384 HMAC
* RTE_CRYPTO_AUTH_SHA3_512
* RTE_CRYPTO_AUTH_SHA3_512 HMAC
+* RTE_CRYPTO_AUTH_SHAKE_128
+* RTE_CRYPTO_AUTH_SHAKE_256
AEAD algorithms:
diff --git a/doc/guides/cryptodevs/features/aesni_mb.ini b/doc/guides/cryptodevs/features/aesni_mb.ini
index ff7fcceb036..dca241b7f34 100644
--- a/doc/guides/cryptodevs/features/aesni_mb.ini
+++ b/doc/guides/cryptodevs/features/aesni_mb.ini
@@ -77,6 +77,8 @@ SHA3-384 = Y
SHA3-384 HMAC = Y
SHA3-512 = Y
SHA3-512 HMAC = Y
+SHAKE-128 = Y
+SHAKE-256 = Y
;
; Supported AEAD algorithms of the 'aesni_mb' crypto driver.
diff --git a/doc/guides/rel_notes/release_26_11.rst b/doc/guides/rel_notes/release_26_11.rst
index 826a0cf05cf..c116f3373da 100644
--- a/doc/guides/rel_notes/release_26_11.rst
+++ b/doc/guides/rel_notes/release_26_11.rst
@@ -28,6 +28,7 @@ New Features
* Added support for SHA3-224, SHA3-256, SHA3-384, and SHA3-512 hash
algorithms and their HMAC variants.
+ * Added support for SHAKE-128 and SHAKE-256 hash algorithms.
.. This section should contain new features added in this release.
Sample format:
diff --git a/drivers/crypto/ipsec_mb/pmd_aesni_mb.c b/drivers/crypto/ipsec_mb/pmd_aesni_mb.c
index a63f9671528..d9d7366da39 100644
--- a/drivers/crypto/ipsec_mb/pmd_aesni_mb.c
+++ b/drivers/crypto/ipsec_mb/pmd_aesni_mb.c
@@ -331,6 +331,14 @@ aesni_mb_set_session_auth_parameters(IMB_MGR *mb_mgr,
case RTE_CRYPTO_AUTH_SHA3_512_HMAC:
sess->template_job.hash_alg = IMB_AUTH_HMAC_SHA3_512;
break;
+ case RTE_CRYPTO_AUTH_SHAKE_128:
+ sess->template_job.hash_alg = IMB_AUTH_SHAKE128;
+ auth_precompute = 0;
+ break;
+ case RTE_CRYPTO_AUTH_SHAKE_256:
+ sess->template_job.hash_alg = IMB_AUTH_SHAKE256;
+ auth_precompute = 0;
+ break;
#endif
default:
IPSEC_MB_LOG(ERR,
diff --git a/drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h b/drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h
index 6fdb4b8e1fb..25dc7151b09 100644
--- a/drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h
+++ b/drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h
@@ -937,6 +937,48 @@ static const struct rte_cryptodev_capabilities aesni_mb_capabilities[] = {
}, }
}, }
},
+ { /* SHAKE-128 */
+ .op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
+ {.sym = {
+ .xform_type = RTE_CRYPTO_SYM_XFORM_AUTH,
+ {.auth = {
+ .algo = RTE_CRYPTO_AUTH_SHAKE_128,
+ .block_size = 168,
+ .key_size = {
+ .min = 0,
+ .max = 0,
+ .increment = 0
+ },
+ .digest_size = {
+ .min = 1,
+ .max = 65535,
+ .increment = 1
+ },
+ .iv_size = { 0 }
+ }, }
+ }, }
+ },
+ { /* SHAKE-256 */
+ .op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
+ {.sym = {
+ .xform_type = RTE_CRYPTO_SYM_XFORM_AUTH,
+ {.auth = {
+ .algo = RTE_CRYPTO_AUTH_SHAKE_256,
+ .block_size = 136,
+ .key_size = {
+ .min = 0,
+ .max = 0,
+ .increment = 0
+ },
+ .digest_size = {
+ .min = 1,
+ .max = 65535,
+ .increment = 1
+ },
+ .iv_size = { 0 }
+ }, }
+ }, }
+ },
#endif
{ /* SM4 CBC */
.op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
@@ -1073,7 +1115,9 @@ static const unsigned int auth_blocksize[] = {
[IMB_AUTH_HMAC_SHA3_224] = 144,
[IMB_AUTH_HMAC_SHA3_256] = 136,
[IMB_AUTH_HMAC_SHA3_384] = 104,
- [IMB_AUTH_HMAC_SHA3_512] = 72
+ [IMB_AUTH_HMAC_SHA3_512] = 72,
+ [IMB_AUTH_SHAKE128] = 168,
+ [IMB_AUTH_SHAKE256] = 136
#endif
};
@@ -1117,7 +1161,9 @@ static const unsigned int auth_truncated_digest_byte_lengths[] = {
[IMB_AUTH_HMAC_SHA3_224] = 28,
[IMB_AUTH_HMAC_SHA3_256] = 32,
[IMB_AUTH_HMAC_SHA3_384] = 48,
- [IMB_AUTH_HMAC_SHA3_512] = 64
+ [IMB_AUTH_HMAC_SHA3_512] = 64,
+ [IMB_AUTH_SHAKE128] = 64,
+ [IMB_AUTH_SHAKE256] = 64
#endif
};
@@ -1165,7 +1211,9 @@ static const unsigned int auth_digest_byte_lengths[] = {
[IMB_AUTH_HMAC_SHA3_224] = 28,
[IMB_AUTH_HMAC_SHA3_256] = 32,
[IMB_AUTH_HMAC_SHA3_384] = 48,
- [IMB_AUTH_HMAC_SHA3_512] = 64
+ [IMB_AUTH_HMAC_SHA3_512] = 64,
+ [IMB_AUTH_SHAKE128] = 64,
+ [IMB_AUTH_SHAKE256] = 64
#endif
/**< Vector mode dependent pointer table of the multi-buffer APIs */
--
2.43.0
prev parent reply other threads:[~2026-10-05 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 12:30 [PATCH 1/2] crypto/ipsec_mb: Add SHA3 support Emma Finn
2026-10-05 12:30 ` Emma Finn [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=20261005123041.429121-2-emma.finn@intel.com \
--to=emma.finn@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.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