DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Power, Ciara" <ciara.power@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>, "Ji, Kai" <kai.ji@intel.com>
Subject: RE: [PATCH v3] crypto/qat: add SM3 HMAC to gen4 devices
Date: Fri, 16 Jun 2023 08:57:36 +0000	[thread overview]
Message-ID: <SN7PR11MB76394C0BB48A3ED2EA0E85ABE658A@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230614175623.153833-1-arkadiuszx.kusztal@intel.com>

Hi Arek,

> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Wednesday 14 June 2023 18:56
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Ji, Kai <kai.ji@intel.com>; Power, Ciara
> <ciara.power@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v3] crypto/qat: add SM3 HMAC to gen4 devices
> 
> This commit adds SM3 HMAC to Intel QuickAssist Technology PMD
> generation 3 and 4 devices.
> 
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> 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 +
>  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(-)
> 

Acked-by: Ciara Power <ciara.power@intel.com>

  reply	other threads:[~2023-06-16  8:57 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 [this message]
2023-06-20  8:30 ` [EXT] " 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=SN7PR11MB76394C0BB48A3ED2EA0E85ABE658A@SN7PR11MB7639.namprd11.prod.outlook.com \
    --to=ciara.power@intel.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).