From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: fiona.trahe@intel.com, pablo.de.lara.guarch@intel.com,
john.griffin@intel.com, deepak.k.jain@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/3] Add ZUC EEA3/EIA3 capability to Intel(R) QuickAssist Technology driver
Date: Wed, 29 Mar 2017 14:04:16 +0100 [thread overview]
Message-ID: <1490792659-31544-1-git-send-email-arkadiuszx.kusztal@intel.com> (raw)
This patchset add ZUC cipher (EEA3) and MAC (EIA3) capability to Intel(R) QuickAssist Technology
driver and corresponding test cases to cryptodev test files.
This patchset depends on the following patches/patchsets:
"crypto/qat: fix segmentation fault in session create"
(http://dpdk.org/dev/patchwork/patch/22692/)
v2:
- added EIA3 MAC capability
- changed capabilities structure to enable ZUC capability checks
- added generic wireless test functions
Arek Kusztal (3):
crypto/qat: refactor capabilities infrastructure
crypto/qat: add ZUC EEA3/EIA3 capability
test: add ZUC test cases for QAT
doc/guides/cryptodevs/features/qat.ini | 2 +
doc/guides/cryptodevs/qat.rst | 3 +
doc/guides/rel_notes/release_17_05.rst | 6 +
drivers/crypto/qat/qat_adf/qat_algs.h | 11 +-
drivers/crypto/qat/qat_adf/qat_algs_build_desc.c | 126 ++++-
drivers/crypto/qat/qat_crypto.c | 578 +++-------------------
drivers/crypto/qat/qat_crypto.h | 3 +
drivers/crypto/qat/qat_crypto_capabilities.h | 554 +++++++++++++++++++++
drivers/crypto/qat/rte_qat_cryptodev.c | 24 +
test/test/test_cryptodev.c | 327 ++++++++++++-
test/test/test_cryptodev_zuc_hash_test_vectors.h | 359 --------------
test/test/test_cryptodev_zuc_test_vectors.h | 598 ++++++++++++++++++++++-
12 files changed, 1674 insertions(+), 917 deletions(-)
create mode 100644 drivers/crypto/qat/qat_crypto_capabilities.h
delete mode 100644 test/test/test_cryptodev_zuc_hash_test_vectors.h
--
2.7.4
next reply other threads:[~2017-03-29 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 13:04 Arek Kusztal [this message]
2017-03-29 13:04 ` [dpdk-dev] [PATCH v2 1/3] crypto/qat: refactor capabilities infrastructure Arek Kusztal
2017-03-30 13:34 ` Trahe, Fiona
2017-03-30 21:50 ` De Lara Guarch, Pablo
2017-03-29 13:04 ` [dpdk-dev] [PATCH v2 2/3] crypto/qat: add ZUC EEA3/EIA3 capability Arek Kusztal
2017-03-30 13:35 ` Trahe, Fiona
2017-03-29 13:04 ` [dpdk-dev] [PATCH v2 3/3] test: add ZUC test cases for QAT Arek Kusztal
2017-03-30 13:36 ` Trahe, Fiona
2017-03-30 21:29 ` De Lara Guarch, Pablo
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=1490792659-31544-1-git-send-email-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@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).