From: "Kumar, Ravi1" <Ravi1.Kumar@amd.com>
To: "Sardar, Shamsher singh" <Shamshersingh.Sardar@amd.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] crypto/ccp: sha3 support enabling in ccp
Date: Wed, 22 Jan 2020 11:11:29 +0000 [thread overview]
Message-ID: <MW2PR12MB2570F5721CB98D491E8AA989AE0C0@MW2PR12MB2570.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20200122105222.3758-1-ssardar@amd.com>
[AMD Official Use Only - Internal Distribution Only]
For series,
Acked-by: Ravi Kumar <ravi1.kumar@amd.com>
Regards,
Ravi
>-----Original Message-----
>From: Sardar, Shamsher singh <Shamshersingh.Sardar@amd.com>
>Sent: Wednesday, January 22, 2020 4:22 PM
>To: dev@dpdk.org
>Cc: Kumar, Ravi1 <Ravi1.Kumar@amd.com>
>Subject: [PATCH v2 1/2] crypto/ccp: sha3 support enabling in ccp
>
>From: Sardar Shamsher Singh <Shamshersingh.Sardar@amd.com>
>
>sha3 support enabled in AMD-CCP crypto controller
>
>Signed-off-by: Sardar Shamsher Singh <Shamshersingh.Sardar@amd.com>
>---
> lib/librte_cryptodev/rte_cryptodev.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
>diff --git a/lib/librte_cryptodev/rte_cryptodev.c b/lib/librte_cryptodev/rte_cryptodev.c
>index 5c6359b5c..6ee4f1086 100644
>--- a/lib/librte_cryptodev/rte_cryptodev.c
>+++ b/lib/librte_cryptodev/rte_cryptodev.c
>@@ -140,7 +140,16 @@ 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_SHA3_224] = "sha3-224",
>+ [RTE_CRYPTO_AUTH_SHA3_224_HMAC] = "sha3-224-hmac",
>+ [RTE_CRYPTO_AUTH_SHA3_256] = "sha3-256",
>+ [RTE_CRYPTO_AUTH_SHA3_256_HMAC] = "sha3-256-hmac",
>+ [RTE_CRYPTO_AUTH_SHA3_384] = "sha3-384",
>+ [RTE_CRYPTO_AUTH_SHA3_384_HMAC] = "sha3-384-hmac",
>+ [RTE_CRYPTO_AUTH_SHA3_512] = "sha3-512",
>+ [RTE_CRYPTO_AUTH_SHA3_512_HMAC] = "sha3-512-hmac"
> };
>
> /**
>--
>2.17.1
>
next prev parent reply other threads:[~2020-01-22 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 10:52 ssardar
2020-01-22 10:52 ` [dpdk-dev] [PATCH v2 2/2] examples/crypto: crypto test application ssardar
2020-01-28 6:35 ` Akhil Goyal
2020-01-30 8:45 ` Sardar, Shamsher singh
2020-01-30 8:52 ` Akhil Goyal
2020-01-30 9:08 ` Sardar, Shamsher singh
2020-01-22 11:11 ` Kumar, Ravi1 [this message]
2020-02-05 12:24 ` [dpdk-dev] [PATCH v2 1/2] crypto/ccp: sha3 support enabling in ccp Akhil Goyal
2020-02-05 22:22 ` Thomas Monjalon
2020-02-06 9:34 ` David Marchand
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=MW2PR12MB2570F5721CB98D491E8AA989AE0C0@MW2PR12MB2570.namprd12.prod.outlook.com \
--to=ravi1.kumar@amd.com \
--cc=Shamshersingh.Sardar@amd.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;
as well as URLs for NNTP newsgroup(s).