From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, kai.ji@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [PATCH v2 0/4] crypto/qat: extend asymmetric crypto pmd
Date: Thu, 20 Oct 2022 16:09:36 +0100 [thread overview]
Message-ID: <20221020150940.62465-1-arkadiuszx.kusztal@intel.com> (raw)
This patchset extends Intel QuickAssist Technology asymmetric crypto PMD.
Following features were added:
- ECDH algorithm handling
- EC point verification
Depends-on: series-25284 ("crypto/qat: fix uncleared cookies in asym")
v2:
- resolved compilation issues
- improved code structure
Arek Kusztal (4):
crypto/qat: make immutable parameters constant
crypto/qat: improve freeing of asym cookies
crypto/qat: add ecdh key exchange algorithm
crypto/qat: add ecdh public key verification
doc/guides/cryptodevs/features/qat.ini | 7 +-
doc/guides/cryptodevs/qat.rst | 1 +
doc/guides/rel_notes/release_22_11.rst | 4 +
drivers/common/qat/qat_adf/qat_pke.h | 40 ++++-
drivers/common/qat/qat_device.c | 2 +-
drivers/common/qat/qat_device.h | 4 +-
drivers/crypto/qat/qat_asym.c | 317 ++++++++++++++++++++++++---------
drivers/crypto/qat/qat_ec.h | 2 +-
8 files changed, 274 insertions(+), 103 deletions(-)
--
2.13.6
next reply other threads:[~2022-10-20 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 15:09 Arek Kusztal [this message]
2022-10-20 15:09 ` [PATCH v2 1/4] crypto/qat: make immutable parameters constant Arek Kusztal
2022-10-20 21:55 ` Ji, Kai
2022-10-20 15:09 ` [PATCH v2 2/4] crypto/qat: improve freeing of asym cookies Arek Kusztal
2022-10-20 21:57 ` Ji, Kai
2022-10-20 15:09 ` [PATCH v2 3/4] crypto/qat: add ecdh key exchange algorithm Arek Kusztal
2022-10-24 11:11 ` Ji, Kai
2022-10-20 15:09 ` [PATCH v2 4/4] crypto/qat: add ecdh public key verification Arek Kusztal
2022-10-24 11:26 ` Ji, Kai
2022-10-27 9:48 ` [EXT] [PATCH v2 0/4] crypto/qat: extend asymmetric crypto pmd 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=20221020150940.62465-1-arkadiuszx.kusztal@intel.com \
--to=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).