From: Piotr Azarewicz <piotrx.t.azarewicz@intel.com>
To: pablo.de.lara.guarch@intel.com, dev@dpdk.org
Subject: [dpdk-dev] [PATCH v6 0/2] crypto/aesni_gcm: migration from MB library to ISA-L
Date: Tue, 17 Jan 2017 12:19:17 +0100 [thread overview]
Message-ID: <1484651959-9527-1-git-send-email-piotrx.t.azarewicz@intel.com> (raw)
In-Reply-To: <1484570243-218696-1-git-send-email-piotrx.t.azarewicz@intel.com>
Current Cryptodev AES-NI GCM PMD is implemented using Multi Buffer
Crypto library.This patch reimplement the device using ISA-L Crypto
library: https://github.com/01org/isa-l_crypto.
The migration entailed the following additional support for:
* GMAC algorithm.
* 256-bit cipher key.
* Session-less mode.
* Out-of place processing
* Scatter-gatter support for chained mbufs (only out-of place and
destination mbuf must be contiguous)
Verified current unit tests and added new unit tests to verify new
functionalities.
Signed-off-by: Piotr Azarewicz <piotrx.t.azarewicz@intel.com>
Acked-by: Declan Doherty <declan.doherty@intel.com>
v6 changes:
- rebase on top of dpdk-next-crypto
- split driver implementation and tests
v5 changes:
- rebase on top of dpdk-next-crypto
- remove the perftest output from commit message
- correction in aesni_gcm.rst
- fix typo
v4 changes:
- rebase on top of dpdk-next-crypto
- update the script test-build.sh
v3 changes:
- rebase on top of dpdk-next-crypto
v2 changes:
- implement native scatter-gatter support for chained mbufs (only out-of
place and destination mbuf must be contiguous)
- write unit test for session-less mode
- write unit test for out-of place processing
- add support for GMAC authentication algorithm
Piotr Azarewicz (2):
crypto/aesni_gcm: migration from MB library to ISA-L
app/test: add GCM additional tests
app/test/test_cryptodev.c | 753 +++++++++++++++++++---
app/test/test_cryptodev_gcm_test_vectors.h | 491 +++++++++++++-
devtools/test-build.sh | 4 +-
doc/guides/cryptodevs/aesni_gcm.rst | 24 +-
doc/guides/rel_notes/release_17_02.rst | 12 +
drivers/crypto/aesni_gcm/Makefile | 8 +-
drivers/crypto/aesni_gcm/aesni_gcm_ops.h | 95 +--
drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 320 +++++----
drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c | 49 +-
drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h | 15 +-
mk/rte.app.mk | 3 +-
11 files changed, 1361 insertions(+), 413 deletions(-)
--
1.7.9.5
next prev parent reply other threads:[~2017-01-17 11:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 18:53 [dpdk-dev] [PATCH v2] " Michal Jastrzebski
2017-01-03 13:02 ` [dpdk-dev] [PATCH v3] " Piotr Azarewicz
2017-01-03 14:14 ` Thomas Monjalon
2017-01-05 13:51 ` [dpdk-dev] [PATCH v4] " Piotr Azarewicz
2017-01-05 15:12 ` Thomas Monjalon
2017-01-16 12:37 ` [dpdk-dev] [PATCH v5] " Piotr Azarewicz
2017-01-16 14:42 ` Thomas Monjalon
2017-01-16 15:20 ` Mcnamara, John
2017-01-16 14:43 ` Thomas Monjalon
2017-01-17 7:42 ` Azarewicz, PiotrX T
2017-01-16 16:05 ` Declan Doherty
2017-01-17 11:19 ` Piotr Azarewicz [this message]
2017-01-17 11:19 ` [dpdk-dev] [PATCH v6 1/2] " Piotr Azarewicz
2017-01-17 11:19 ` [dpdk-dev] [PATCH v6 2/2] app/test: add GCM additional tests Piotr Azarewicz
2017-01-18 12:37 ` [dpdk-dev] [PATCH v6 0/2] crypto/aesni_gcm: migration from MB library to ISA-L 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=1484651959-9527-1-git-send-email-piotrx.t.azarewicz@intel.com \
--to=piotrx.t.azarewicz@intel.com \
--cc=dev@dpdk.org \
--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).