From: Sunyang Wu <sunyang.wu@jaguarmicro.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "kai.ji@intel.com" <kai.ji@intel.com>
Subject: 回复: [EXT] [PATCH 1/2] lib/cryptodev/: Add SM3_HMAC/SM4_CFB/SM4_OFB support in DPDK
Date: Thu, 25 May 2023 09:00:37 +0000 [thread overview]
Message-ID: <KL1PR0601MB5567F13C5C1D7D9172ADBAC790469@KL1PR0601MB5567.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB448466828461B9DB6BE92CAED8469@CO6PR18MB4484.namprd18.prod.outlook.com>
Hi Akhil,
The patches have been resubmitted.
Best wishes
sunyang
-----Original Message-----
From: Akhil Goyal <gakhil@marvell.com>
Send: 2023.5.25 16:27 PM
To: Akhil Goyal <gakhil@marvell.com>; Sunyang Wu <sunyang.wu@jaguarmicro.com>; dev@dpdk.org
Cc: kai.ji@intel.com
Subject: RE: [EXT] [PATCH 1/2] lib/cryptodev/: Add SM3_HMAC/SM4_CFB/SM4_OFB support in DPDK
Hi Sunyang,
Can you send the next version for this patch?
We need to merge in RC1 (31st May).
> Subject: RE: [EXT] [PATCH 1/2] lib/cryptodev/: Add
> SM3_HMAC/SM4_CFB/SM4_OFB support in DPDK
>
> > Add SM3_HMAC/SM4_CFB/SM4_OFB support in DPDK.
> >
> > Signed-off-by: Sunyang Wu <sunyang.wu@jaguarmicro.com>
> > ---
> > lib/cryptodev/rte_crypto_sym.h | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
>
> Please add release notes and update
> doc/guides/cryptodevs/features/default.ini.
>
> The update to crypto_auth/cipher_algorithm_strings is also missing.
>
> > diff --git a/lib/cryptodev/rte_crypto_sym.h
> > b/lib/cryptodev/rte_crypto_sym.h index 2cfe66530c..c4572106dc 100644
> > --- a/lib/cryptodev/rte_crypto_sym.h
> > +++ b/lib/cryptodev/rte_crypto_sym.h
> > @@ -172,8 +172,12 @@ enum rte_crypto_cipher_algorithm {
> > /**< ShangMi 4 (SM4) algorithm in ECB mode */
> > RTE_CRYPTO_CIPHER_SM4_CBC,
> > /**< ShangMi 4 (SM4) algorithm in CBC mode */
> > - RTE_CRYPTO_CIPHER_SM4_CTR
> > + RTE_CRYPTO_CIPHER_SM4_CTR,
> > /**< ShangMi 4 (SM4) algorithm in CTR mode */
> > + RTE_CRYPTO_CIPHER_SM4_OFB,
> > + /**< ShangMi 4 (SM4) algorithm in OFB mode */
> > + RTE_CRYPTO_CIPHER_SM4_CFB
> > + /**< ShangMi 4 (SM4) algorithm in CFB mode */
> > };
> >
> > /** Cipher algorithm name strings */ @@ -376,6 +380,8 @@ enum
> > rte_crypto_auth_algorithm {
> > /**< HMAC using 512 bit SHA3 algorithm. */
> > RTE_CRYPTO_AUTH_SM3,
> > /**< ShangMi 3 (SM3) algorithm */
> > + RTE_CRYPTO_AUTH_SM3_HMAC,
> > + /** < HMAC using Chinese SM3 algorithm */
> >
> > RTE_CRYPTO_AUTH_SHAKE_128,
> > /**< 128 bit SHAKE algorithm. */
> > --
> > 2.19.0.rc0.windows.1
next prev parent reply other threads:[~2023-05-25 9:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 3:10 Sunyang Wu
2023-03-16 3:10 ` [PATCH 2/2] test/crypto: Add SM3/SM4 test vectors for verification in test app Sunyang Wu
2023-03-16 10:42 ` [EXT] [PATCH 1/2] lib/cryptodev/: Add SM3_HMAC/SM4_CFB/SM4_OFB support in DPDK Akhil Goyal
2023-03-18 13:00 ` 回复: " Sunyang Wu
2023-04-19 19:41 ` Kusztal, ArkadiuszX
2023-05-17 7:04 ` Akhil Goyal
2023-05-25 8:27 ` Akhil Goyal
2023-05-25 9:00 ` Sunyang Wu [this message]
2023-05-25 9:04 ` Akhil Goyal
2023-05-25 9:25 ` 回复: " Sunyang Wu
2023-05-25 9:45 ` 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=KL1PR0601MB5567F13C5C1D7D9172ADBAC790469@KL1PR0601MB5567.apcprd06.prod.outlook.com \
--to=sunyang.wu@jaguarmicro.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).