From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Dooley, Brian" <brian.dooley@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"Ji, Kai" <kai.ji@intel.com>
Subject: RE: [PATCH v3 1/2] crypto/ipsec_mb: add SM4 GCM support
Date: Tue, 18 Feb 2025 10:48:14 +0000 [thread overview]
Message-ID: <CO6PR11MB5587187C907F0E63A9BE306B84FA2@CO6PR11MB5587.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250113171022.1649181-1-brian.dooley@intel.com>
Hi Brian,
> -----Original Message-----
> From: Dooley, Brian <brian.dooley@intel.com>
> Sent: Monday, January 13, 2025 6:10 PM
> Cc: dev@dpdk.org; gakhil@marvell.com; Ji, Kai <kai.ji@intel.com>; De Lara
> Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Dooley, Brian
> <brian.dooley@intel.com>
> Subject: [PATCH v3 1/2] crypto/ipsec_mb: add SM4 GCM support
>
> This patch introduces SM4 GCM algorithm support to the AESNI_MB PMD.
> SM4 GCM is available in the v2.0 release of Intel IPsec MB.
>
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
> ---
A couple of comments below.
Thanks,
Pablo
...
> --- a/drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h
> +++ b/drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h
> @@ -826,6 +826,36 @@ static const struct rte_cryptodev_capabilities
> aesni_mb_capabilities[] = {
> }, }
> }, }
> },
> + { /* SM4 GCM */
> + .op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
> + {.sym = {
> + .xform_type = RTE_CRYPTO_SYM_XFORM_AEAD,
> + {.aead = {
> + .algo = RTE_CRYPTO_AEAD_SM4_GCM,
> + .block_size = 16,
> + .key_size = {
> + .min = 16,
> + .max = 16,
> + .increment = 0,
> + },
> + .digest_size = {
> + .min = 16,
> + .max = 16,
> + .increment = 0,
Digest size can be 1 to 16 bytes.
> + },
> + .aad_size = {
> + .min = 0,
> + .max = 65535,
> + .increment = 1,
> + },
> + .iv_size = {
> + .min = 12,
> + .max = 12,
> + .increment = 0,
> + }
> + }, }
> + }, }
> + },
> #endif
> RTE_CRYPTODEV_END_OF_CAPABILITIES_LIST()
> };
> diff --git a/lib/cryptodev/rte_crypto_sym.h b/lib/cryptodev/rte_crypto_sym.h
> index 505356ff44..b47e52f63b 100644
> --- a/lib/cryptodev/rte_crypto_sym.h
> +++ b/lib/cryptodev/rte_crypto_sym.h
> @@ -482,8 +482,10 @@ enum rte_crypto_aead_algorithm {
> /**< AES algorithm in CCM mode. */
> RTE_CRYPTO_AEAD_AES_GCM,
> /**< AES algorithm in GCM mode. */
> - RTE_CRYPTO_AEAD_CHACHA20_POLY1305
> + RTE_CRYPTO_AEAD_CHACHA20_POLY1305,
> /**< Chacha20 cipher with poly1305 authenticator */
> + RTE_CRYPTO_AEAD_SM4_GCM
> + /**< SM4 cipher with GCM mode */
To keep consistency, "in GCM mode".
> };
next prev parent reply other threads:[~2025-02-18 10:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 12:58 [PATCH v1 " Brian Dooley
2024-12-13 12:58 ` [PATCH v1 2/2] app/test: add SM4 GCM tests Brian Dooley
2025-01-13 16:39 ` [PATCH v2 1/2] crypto/ipsec_mb: add SM4 GCM support Brian Dooley
2025-01-13 16:39 ` Brian Dooley
2025-01-13 17:10 ` [PATCH v3 " Brian Dooley
2025-01-13 17:10 ` [PATCH v3 2/2] app/test: add SM4 GCM tests Brian Dooley
2025-01-29 9:32 ` Dooley, Brian
2025-02-18 11:01 ` De Lara Guarch, Pablo
2025-02-06 12:51 ` [EXTERNAL] [PATCH v3 1/2] crypto/ipsec_mb: add SM4 GCM support Akhil Goyal
2025-02-18 10:48 ` De Lara Guarch, Pablo [this message]
2025-02-19 11:49 ` [PATCH v4 1/3] " Brian Dooley
2025-02-19 11:50 ` [PATCH v4 2/3] cryptodev: add SM4 GCM Brian Dooley
2025-02-20 15:40 ` De Lara Guarch, Pablo
2025-02-19 11:50 ` [PATCH v4 3/3] app/test: add SM4 GCM tests Brian Dooley
2025-02-20 15:39 ` [PATCH v4 1/3] crypto/ipsec_mb: add SM4 GCM support De Lara Guarch, Pablo
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=CO6PR11MB5587187C907F0E63A9BE306B84FA2@CO6PR11MB5587.namprd11.prod.outlook.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@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).