From: Anoob Joseph <anoobj@marvell.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Cc: Akhil Goyal <gakhil@marvell.com>,
"kai.ji@intel.com" <kai.ji@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] [PATCH 2/4] cryptodev: add SM3 hash algorithm
Date: Wed, 17 Aug 2022 10:35:01 +0000 [thread overview]
Message-ID: <PH0PR18MB46724EE266F05989BEE0A4D8DF6A9@PH0PR18MB4672.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220817060856.78582-3-arkadiuszx.kusztal@intel.com>
Hi Arek,
Please see inline.
Thanks,
Anoob
>
> External Email
>
> ----------------------------------------------------------------------
> SM3 is a cryptographic hash function used in the Chinese National Standard.
>
> - Added SM3 algorithm
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
[snip]
> a/lib/cryptodev/rte_cryptodev.c b/lib/cryptodev/rte_cryptodev.c index
> 266804f0fe..2b6c7de930 100644
> --- a/lib/cryptodev/rte_cryptodev.c
> +++ b/lib/cryptodev/rte_cryptodev.c
> @@ -135,7 +135,8 @@ rte_crypto_auth_algorithm_strings[] = {
>
> [RTE_CRYPTO_AUTH_KASUMI_F9] = "kasumi-f9",
> [RTE_CRYPTO_AUTH_SNOW3G_UIA2] = "snow3g-uia2",
> - [RTE_CRYPTO_AUTH_ZUC_EIA3] = "zuc-eia3"
> + [RTE_CRYPTO_AUTH_ZUC_EIA3] = "zuc-eia3",
> + [RTE_CRYPTO_AUTH_SM3] = "zuc-sm3"
[Anoob] Should the string be "sm3" instead of "zuc-sm3"?
next prev parent reply other threads:[~2022-08-17 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 6:08 [PATCH 0/4] cryptodev: add SM3 and SM4 algorithms Arek Kusztal
2022-08-17 6:08 ` [PATCH 1/4] cryptodev: add SM4 encryption algorithm Arek Kusztal
2022-08-17 6:08 ` [PATCH 2/4] cryptodev: add SM3 hash algorithm Arek Kusztal
2022-08-17 10:35 ` Anoob Joseph [this message]
2022-08-17 6:08 ` [PATCH 3/4] crypto/qat: add SM4 encryption algorithm Arek Kusztal
2022-08-17 6:08 ` [PATCH 4/4] crypto/qat : add SM3 hash algorithm Arek Kusztal
2022-09-21 19:34 ` [EXT] " Akhil Goyal
2022-09-21 19:37 ` [EXT] [PATCH 0/4] cryptodev: add SM3 and SM4 algorithms Akhil Goyal
2022-09-28 10:56 ` Kusztal, ArkadiuszX
2022-09-28 11:05 ` Akhil Goyal
2022-09-28 11:49 ` Kusztal, ArkadiuszX
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=PH0PR18MB46724EE266F05989BEE0A4D8DF6A9@PH0PR18MB4672.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@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).