From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: akhil.goyal@nxp.com, fiona.trahe@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-dev] [PATCH v4 0/4] Add PMD for asymmetric cryptography operations using Intel QuickAssist Technology devices
Date: Wed, 27 Mar 2019 12:17:16 +0100 [thread overview]
Message-ID: <20190327111720.13732-1-arkadiuszx.kusztal@intel.com> (raw)
This patchset adds Poll Mode Driver to use asymmetric cryptography
functions using Intel QuickAssist Techology devices.
Following functions are available with this patchset:
* Modular Exponentiation
* Modular Inverse
This patch depends on a QAT PF driver for device initialization. See
the file docs/guides/cryptodevs/qat.rst for configuration details.
Limitations:
* Maximum parameter size: 4096 bits
- For both modular exponentiaion and modular multiplicative inverse
v4:
- fixed yet more checkpatch issues
v3:
- fixed some checkpatch issues
v2:
- added Meson build
- fixed segfault on cookie
- fixed mod inverse problem
Arek Kusztal (4):
common/qat: add headers for asymmetric crypto
crypto/qat: add asymmetric cryptography PMD
crypto/qat: add modular exponentiation to qat asym pmd
crypto/qat: add modular inverse to qat asym pmd
config/common_base | 1 +
doc/guides/cryptodevs/qat.rst | 10 +
drivers/common/qat/Makefile | 8 +
drivers/common/qat/qat_adf/icp_qat_fw_mmp_ids.h | 1538 ++++++++++++++++++++
drivers/common/qat/qat_adf/icp_qat_fw_pke.h | 426 ++++++
.../qat/qat_adf/qat_pke_functionality_arrays.h | 52 +
drivers/common/qat/qat_device.h | 12 +-
drivers/common/qat/qat_qp.c | 8 +
drivers/crypto/qat/meson.build | 5 +-
drivers/crypto/qat/qat_asym.c | 419 ++++++
drivers/crypto/qat/qat_asym.h | 106 ++
drivers/crypto/qat/qat_asym_capabilities.h | 42 +
drivers/crypto/qat/qat_asym_pmd.c | 309 ++++
drivers/crypto/qat/qat_asym_pmd.h | 50 +
drivers/crypto/qat/qat_sym_pmd.c | 1 -
drivers/crypto/qat/qat_sym_pmd.h | 3 +-
mk/rte.app.mk | 1 +
17 files changed, 2986 insertions(+), 5 deletions(-)
create mode 100644 drivers/common/qat/qat_adf/icp_qat_fw_mmp_ids.h
create mode 100644 drivers/common/qat/qat_adf/icp_qat_fw_pke.h
create mode 100644 drivers/common/qat/qat_adf/qat_pke_functionality_arrays.h
create mode 100644 drivers/crypto/qat/qat_asym.c
create mode 100644 drivers/crypto/qat/qat_asym.h
create mode 100644 drivers/crypto/qat/qat_asym_capabilities.h
create mode 100644 drivers/crypto/qat/qat_asym_pmd.c
create mode 100644 drivers/crypto/qat/qat_asym_pmd.h
--
2.1.0
next reply other threads:[~2019-03-27 11:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 11:17 Arek Kusztal [this message]
2019-03-27 11:17 ` Arek Kusztal
2019-03-27 11:17 ` [dpdk-dev] [PATCH v4 1/4] common/qat: add headers for asymmetric crypto Arek Kusztal
2019-03-27 11:17 ` Arek Kusztal
2019-03-27 11:17 ` [dpdk-dev] [PATCH v4 2/4] crypto/qat: add asymmetric cryptography PMD Arek Kusztal
2019-03-27 11:17 ` Arek Kusztal
2019-03-27 18:19 ` Trahe, Fiona
2019-03-27 18:19 ` Trahe, Fiona
2019-03-27 11:17 ` [dpdk-dev] [PATCH v4 3/4] crypto/qat: add modular exponentiation to qat asym pmd Arek Kusztal
2019-03-27 11:17 ` Arek Kusztal
2019-03-27 11:17 ` [dpdk-dev] [PATCH v4 4/4] crypto/qat: add modular inverse " Arek Kusztal
2019-03-27 11:17 ` 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=20190327111720.13732-1-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).