From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, roy.fan.zhang@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [PATCH v2 0/5] crypto/qat: add asymmetric crypto algorithms
Date: Wed, 9 Feb 2022 14:00:15 +0000 [thread overview]
Message-ID: <20220209140020.19365-1-arkadiuszx.kusztal@intel.com> (raw)
This patchset adds following asymmetric crypto algorithms to Intel QuickAssist Technology driver:
- ECDSA
- ECPM
Code also was refactored to be more readable and easier scalable.
v2:
- add actual implementation
Arek Kusztal (5):
crypto/qat: refactor asymmetric crypto functions
crypto/qat: add named elliptic curves
crypto/qat: add ecdsa algorithm
crypto/qat: add ecpm algorithm
crypto/qat: refactor asymmetric session
doc/guides/cryptodevs/qat.rst | 3 +
doc/guides/rel_notes/release_22_03.rst | 10 +
drivers/common/qat/qat_adf/qat_pke.h | 275 ++++
.../qat/qat_adf/qat_pke_functionality_arrays.h | 79 -
drivers/crypto/qat/dev/qat_asym_pmd_gen1.c | 1 -
drivers/crypto/qat/qat_asym.c | 1662 ++++++++++++--------
drivers/crypto/qat/qat_asym.h | 10 +-
drivers/crypto/qat/qat_ec.h | 206 +++
8 files changed, 1544 insertions(+), 702 deletions(-)
create mode 100644 drivers/common/qat/qat_adf/qat_pke.h
delete mode 100644 drivers/common/qat/qat_adf/qat_pke_functionality_arrays.h
create mode 100644 drivers/crypto/qat/qat_ec.h
--
2.13.6
next reply other threads:[~2022-02-09 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 14:00 Arek Kusztal [this message]
2022-02-09 14:00 ` [PATCH v2 1/5] crypto/qat: refactor asymmetric crypto functions Arek Kusztal
2022-02-09 14:00 ` [PATCH v2 2/5] crypto/qat: add named elliptic curves Arek Kusztal
2022-02-09 14:00 ` [PATCH v2 3/5] crypto/qat: add ecdsa algorithm Arek Kusztal
2022-02-09 14:00 ` [PATCH v2 4/5] crypto/qat: add ecpm algorithm Arek Kusztal
2022-02-09 14:00 ` [PATCH v2 5/5] crypto/qat: refactor asymmetric session Arek Kusztal
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=20220209140020.19365-1-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=roy.fan.zhang@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).