From: Akhil Goyal <gakhil@marvell.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "kai.ji@intel.com" <kai.ji@intel.com>,
"ciara.power@intel.com" <ciara.power@intel.com>
Subject: RE: [EXT] [PATCH v3] crypto/qat: add SM3 HMAC to gen4 devices
Date: Tue, 20 Jun 2023 08:30:43 +0000 [thread overview]
Message-ID: <PH0PR18MB44910EDE291AFB4A78409D09D85CA@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230614175623.153833-1-arkadiuszx.kusztal@intel.com>
> This commit adds SM3 HMAC to Intel QuickAssist Technology PMD
> generation 3 and 4 devices.
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Please be consistent in the signoff names with the .mailmap file.
> ---
> v2:
> - Fixed problem with chaining operations
> - Added implementation of prefix tables
> v3:
> - Added support for gen3 devices
>
> doc/guides/cryptodevs/features/qat.ini | 1 +
> doc/guides/cryptodevs/qat.rst | 5 +
Release notes update is missing.
> drivers/common/qat/qat_adf/icp_qat_fw_la.h | 10 ++
> drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c | 4 +
> drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c | 4 +
> drivers/crypto/qat/dev/qat_crypto_pmd_gens.h | 12 +++
> drivers/crypto/qat/qat_sym_session.c | 100 +++++++++++++++----
> drivers/crypto/qat/qat_sym_session.h | 7 ++
> 8 files changed, 122 insertions(+), 21 deletions(-)
>
> diff --git a/doc/guides/cryptodevs/features/qat.ini
> b/doc/guides/cryptodevs/features/qat.ini
> index 70511a3076..6358a43357 100644
> --- a/doc/guides/cryptodevs/features/qat.ini
> +++ b/doc/guides/cryptodevs/features/qat.ini
> @@ -70,6 +70,7 @@ AES XCBC MAC = Y
> ZUC EIA3 = Y
> AES CMAC (128) = Y
> SM3 = Y
> +SM3 HMAC = Y
>
> ;
> ; Supported AEAD algorithms of the 'qat' crypto driver.
> diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst
> index a4a25711ed..2403430cd6 100644
> --- a/doc/guides/cryptodevs/qat.rst
> +++ b/doc/guides/cryptodevs/qat.rst
> @@ -51,6 +51,9 @@ Cipher algorithms:
> * ``RTE_CRYPTO_CIPHER_AES_DOCSISBPI``
> * ``RTE_CRYPTO_CIPHER_DES_DOCSISBPI``
> * ``RTE_CRYPTO_CIPHER_ZUC_EEA3``
> +* ``RTE_CRYPTO_CIPHER_SM4_ECB``
> +* ``RTE_CRYPTO_CIPHER_SM4_CBC``
> +* ``RTE_CRYPTO_CIPHER_SM4_CTR``
This change should not be part of this patch.
>
> Hash algorithms:
>
> @@ -76,6 +79,8 @@ Hash algorithms:
> * ``RTE_CRYPTO_AUTH_AES_GMAC``
> * ``RTE_CRYPTO_AUTH_ZUC_EIA3``
> * ``RTE_CRYPTO_AUTH_AES_CMAC``
> +* ``RTE_CRYPTO_AUTH_SM3``
> +* ``RTE_CRYPTO_AUTH_SM3_HMAC``
>
> Supported AEAD algorithms:
>
prev parent reply other threads:[~2023-06-20 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 17:56 Arek Kusztal
2023-06-16 8:57 ` Power, Ciara
2023-06-20 8:30 ` Akhil Goyal [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=PH0PR18MB44910EDE291AFB4A78409D09D85CA@PH0PR18MB4491.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--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).