From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: declan.doherty@intel.com
Cc: dev@dpdk.org, Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] [PATCH v3 0/4] AESNI GCM PMD: Migration from ISA-L to Multi-buffer library
Date: Tue, 4 Jul 2017 01:12:39 +0100 [thread overview]
Message-ID: <20170704001243.5130-1-pablo.de.lara.guarch@intel.com> (raw)
In-Reply-To: <20170628113230.83808-1-pablo.de.lara.guarch@intel.com>
This will improve maintainability, as now AESNI GCM PMD will share the same library
as AESNI MB PMD, having one less library to link against. It also adds support for 192-bit keys.
In terms of performance, it has been improved, especially for small packets.
This patchset is migrating the PMD to link against Multi-buffer library v0.46.
Changes in v3:
- Added extra documentation about external library version compatibility.
- Rebased against dpdk-next-crypto
Changes in v2:
- Supported Multi-buffer 0.46 library
- Added new tests to other PMD testsuites
- Rebased against latest dpdk-next-crypto code
Pablo de Lara (4):
crypto/aesni_gcm: migrate to Multi-buffer library
test/crypto: rename some tests
test/crypto: add AES GCM 192 tests
test/crypto: extend AES-GCM 192/256 to other PMDs
devtools/test-build.sh | 4 +-
doc/guides/cryptodevs/aesni_gcm.rst | 53 +-
doc/guides/cryptodevs/features/aesni_gcm.ini | 4 +-
doc/guides/rel_notes/release_17_08.rst | 8 +
drivers/crypto/aesni_gcm/Makefile | 9 +-
drivers/crypto/aesni_gcm/aesni_gcm_ops.h | 97 +++-
drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 111 +++--
drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c | 14 +-
drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h | 28 +-
mk/rte.app.mk | 3 +-
test/test/test_cryptodev.c | 585 ++++++++++++++++-------
test/test/test_cryptodev_gcm_test_vectors.h | 357 ++++++++++++++
12 files changed, 1018 insertions(+), 255 deletions(-)
--
2.9.4
next prev parent reply other threads:[~2017-07-04 8:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 10:16 [dpdk-dev] [PATCH 0/2] " Pablo de Lara
2017-05-26 10:16 ` [dpdk-dev] [PATCH 1/2] crypto/aesni_gcm: migrate " Pablo de Lara
2017-05-26 10:16 ` [dpdk-dev] [PATCH 2/2] test/crypto: add AES GCM 192 tests Pablo de Lara
2017-06-28 11:32 ` [dpdk-dev] [PATCH v2 0/4] AESNI GCM PMD: Migration from ISA-L to Multi-buffer library Pablo de Lara
2017-06-28 11:32 ` [dpdk-dev] [PATCH v2 1/4] crypto/aesni_gcm: migrate " Pablo de Lara
2017-06-28 11:32 ` [dpdk-dev] [PATCH v2 2/4] test/crypto: rename some tests Pablo de Lara
2017-06-28 11:32 ` [dpdk-dev] [PATCH v2 3/4] test/crypto: add AES GCM 192 tests Pablo de Lara
2017-06-28 11:32 ` [dpdk-dev] [PATCH v2 4/4] test/crypto: extend AES-GCM 192/256 to other PMDs Pablo de Lara
2017-06-30 14:16 ` [dpdk-dev] [PATCH v2 0/4] AESNI GCM PMD: Migration from ISA-L to Multi-buffer library Sergio Gonzalez Monroy
2017-07-04 10:11 ` De Lara Guarch, Pablo
2017-07-04 0:12 ` Pablo de Lara [this message]
2017-07-04 0:12 ` [dpdk-dev] [PATCH v3 1/4] crypto/aesni_gcm: migrate " Pablo de Lara
2017-07-04 9:43 ` Declan Doherty
2017-07-04 10:17 ` De Lara Guarch, Pablo
2017-07-04 0:12 ` [dpdk-dev] [PATCH v3 2/4] test/crypto: rename some tests Pablo de Lara
2017-07-04 0:12 ` [dpdk-dev] [PATCH v3 3/4] test/crypto: add AES GCM 192 tests Pablo de Lara
2017-07-04 0:12 ` [dpdk-dev] [PATCH v3 4/4] test/crypto: extend AES-GCM 192/256 to other PMDs Pablo de Lara
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=20170704001243.5130-1-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
/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).