From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-crypto 17.08 rc2
Date: Wed, 19 Jul 2017 15:52:58 +0100 [thread overview]
Message-ID: <20170719145258.61900-1-pablo.de.lara.guarch@intel.com> (raw)
The following changes since commit 838d6b775bfab436859764ea734cddaf95c7b5fd:
mbuf: fix VXLAN port in comment (2017-07-19 09:17:35 +0300)
are available in the git repository at:
http://dpdk.org/git/next/dpdk-next-crypto
for you to fetch changes up to 488587bb9a327f195379ced5650043189d05584d:
examples/l2fwd-crypto: add option to update MAC address (2017-07-19 15:33:07 +0100)
----------------------------------------------------------------
Akhil Goyal (3):
crypto/dpaa2_sec: fix the incorrect free usage for dpsec
crypto/dpaa2_sec: fix typo in PMD name
doc: add missing devices in test-crypto-perf
Arek Kusztal (4):
crypto/qat: remove unused ablkcipher struct and functions
crypto/qat: fix NULL auth hang issue
crypto/qat: fix authentication offset and length for GMAC
crypto/qat: fix handle device-agnostic session
Fan Zhang (1):
crypto/scheduler: fix slave name parsing
Kirill Rybalchenko (4):
doc: extend info on multi-core scheduler
app/crypto-perf: stop crypto devices after test
cryptodev: remove crypto operation status value
crypto/scheduler: fix multicore scheduler reordering
Kuba Kozak (1):
examples/l2fwd-crypto: add option to update MAC address
Pablo de Lara (19):
doc: fix crypto scheduler command line examples
doc: use new crypto driver names
crypto/aesni_mb: fix possible crypto job leak
cryptodev: remove AAD size in auth capabilities
doc: fix supported algorithm table for AESNI GCM PMD
doc: remove incorrect limitation on QAT PMD
doc: remove incorrect limitation on AESNI MB PMD
doc: add missing algorithm in limitations for QAT
doc: extend installation section on SNOW3G/KASUMI PMDs
cryptodev: fix KASUMI F9 expected parameters
crypto/aesni_mb: fix zero burst dequeue
cryptodev: modify some field sizes
cryptodev: rename field name
cryptodev: reorder auth transform
crypto/scheduler: fix buffer not null terminated
examples/l2fwd-crypto: fix digest length
examples/l2fwd-crypto: fix AEAD IV setting
examples/l2fwd-crypto: fix AEAD key setting
crypto/qat: fix session initialization
Srisivasubramanian S (1):
test/crypto-perf: fix ARMV8 session creation
app/test-crypto-perf/cperf_ops.c | 2 +-
app/test-crypto-perf/cperf_test_latency.c | 3 +-
app/test-crypto-perf/cperf_test_throughput.c | 2 +
app/test-crypto-perf/cperf_test_verify.c | 2 +
app/test-crypto-perf/main.c | 1 -
doc/guides/cryptodevs/aesni_mb.rst | 2 +-
doc/guides/cryptodevs/features/aesni_gcm.ini | 1 +
doc/guides/cryptodevs/kasumi.rst | 31 +++-
doc/guides/cryptodevs/qat.rst | 51 ++++--
doc/guides/cryptodevs/scheduler.rst | 8 +-
doc/guides/cryptodevs/snow3g.rst | 11 ++
doc/guides/prog_guide/cryptodev_lib.rst | 4 +-
doc/guides/rel_notes/release_17_08.rst | 5 +
doc/guides/sample_app_ug/ipsec_secgw.rst | 6 +-
doc/guides/sample_app_ug/l2_forward_crypto.rst | 11 +-
doc/guides/tools/cryptoperf.rst | 9 +-
drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 2 +-
drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c | 1 -
drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 10 +-
drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 7 -
drivers/crypto/armv8/rte_armv8_pmd_ops.c | 2 -
drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 4 +-
drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h | 10 +-
drivers/crypto/kasumi/rte_kasumi_pmd.c | 27 +--
drivers/crypto/kasumi/rte_kasumi_pmd_ops.c | 7 +-
drivers/crypto/kasumi/rte_kasumi_pmd_private.h | 1 -
drivers/crypto/null/null_crypto_pmd_ops.c | 1 -
drivers/crypto/openssl/rte_openssl_pmd.c | 2 +-
drivers/crypto/openssl/rte_openssl_pmd_ops.c | 12 --
drivers/crypto/qat/qat_adf/qat_algs.h | 20 +--
drivers/crypto/qat/qat_adf/qat_algs_build_desc.c | 16 +-
drivers/crypto/qat/qat_crypto.c | 168 +++++++++---------
drivers/crypto/qat/qat_crypto.h | 23 ++-
drivers/crypto/qat/qat_crypto_capabilities.h | 24 +--
drivers/crypto/qat/qat_qp.c | 5 +
drivers/crypto/qat/rte_qat_cryptodev.c | 16 +-
drivers/crypto/scheduler/rte_cryptodev_scheduler.c | 14 ++
drivers/crypto/scheduler/rte_cryptodev_scheduler.h | 1 +
drivers/crypto/scheduler/scheduler_multicore.c | 94 +++++++---
drivers/crypto/scheduler/scheduler_pmd.c | 2 +-
drivers/crypto/scheduler/scheduler_pmd_private.h | 3 +-
drivers/crypto/snow3g/rte_snow3g_pmd_ops.c | 3 +-
drivers/crypto/zuc/rte_zuc_pmd_ops.c | 3 +-
examples/ipsec-secgw/sa.c | 4 +-
examples/l2fwd-crypto/main.c | 65 +++++--
lib/librte_cryptodev/rte_crypto.h | 2 -
lib/librte_cryptodev/rte_crypto_sym.h | 59 ++++---
lib/librte_cryptodev/rte_cryptodev.c | 6 +-
lib/librte_cryptodev/rte_cryptodev.h | 4 +-
test/test/test_cryptodev.c | 194 ++++++++++++++-------
test/test/test_cryptodev_hash_test_vectors.h | 36 ++--
.../test/test_cryptodev_kasumi_hash_test_vectors.h | 102 ++---------
test/test/test_cryptodev_kasumi_test_vectors.h | 72 ++++----
test/test/test_cryptodev_perf.c | 6 +-
54 files changed, 666 insertions(+), 511 deletions(-)
next reply other threads:[~2017-07-19 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 14:52 Pablo de Lara [this message]
2017-07-20 15:20 ` Thomas Monjalon
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=20170719145258.61900-1-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).