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 pre-rc1
Date: Sat, 24 Jun 2017 11:37:46 +0100 [thread overview]
Message-ID: <20170624103746.44061-1-pablo.de.lara.guarch@intel.com> (raw)
The following changes since commit 8a04cb6125896e9ea25a4d15a316f0d873822c7b:
pci: set default numa node for broken systems (2017-06-23 15:01:42 +0200)
are available in the git repository at:
http://dpdk.org/git/next/dpdk-next-crypto
for you to fetch changes up to d90d576825aed49bc69eb5547017f064f776afb1:
cryptodev: fix device stop function (2017-06-24 11:20:35 +0100)
----------------------------------------------------------------
Kirill Rybalchenko (1):
cryptodev: fix device stop function
Pablo de Lara (23):
crypto/aesni_gcm: fix leading spaces
examples/l2fwd-crypto: fix option parsing
cryptodev: store device pointer in virtual devices
cryptodev: set driver name for all devices
cryptodev: rename device retrieval argument
cryptodev: simplify device list retrieval logic
cryptodev: only set PCI info when device is PCI
cryptodev: move vdev functions to a separate file
cryptodev: release device if PCI device probing fails
cryptodev: add PCI driver helpers
crypto/qat: do not use cryptodev driver
crypto/dpaa2_sec: do not use cryptodev driver
cryptodev: remove unused PCI probe/remove
cryptodev: remove unused cryptodev driver
crypto/aesni_mb: remove assert check
test/crypto: fix wrong AAD setting
test/crypto: remove unnecessary offset
test/crypto: remove offsets in wireless algorithm vectors
test/crypto: use existing algorithm strings
examples/l2fwd-crypto: fix application help
examples/l2fwd-crypto: fix auth info display
app/crypto-perf: fix error message
doc: fix typo in l2fwd-crypto usage
app/test-crypto-perf/cperf_options_parsing.c | 2 +-
doc/guides/sample_app_ug/l2_forward_crypto.rst | 2 +-
drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 4 +-
drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c | 4 +-
drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 8 +-
drivers/crypto/armv8/rte_armv8_pmd.c | 4 +-
drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 9 +-
drivers/crypto/kasumi/rte_kasumi_pmd.c | 4 +-
drivers/crypto/null/null_crypto_pmd.c | 7 +-
drivers/crypto/openssl/rte_openssl_pmd.c | 4 +-
drivers/crypto/qat/qat_crypto.c | 6 +-
drivers/crypto/qat/qat_qp.c | 8 +-
drivers/crypto/qat/rte_qat_cryptodev.c | 32 ++-
drivers/crypto/scheduler/scheduler_pmd.c | 51 +----
drivers/crypto/scheduler/scheduler_pmd_ops.c | 1 +
drivers/crypto/snow3g/rte_snow3g_pmd.c | 4 +-
drivers/crypto/zuc/rte_zuc_pmd.c | 4 +-
examples/l2fwd-crypto/main.c | 7 +-
lib/librte_cryptodev/Makefile | 2 +
lib/librte_cryptodev/rte_cryptodev.c | 253 +--------------------
lib/librte_cryptodev/rte_cryptodev.h | 39 +---
lib/librte_cryptodev/rte_cryptodev_pci.h | 177 ++++++++++++++
lib/librte_cryptodev/rte_cryptodev_pmd.h | 94 --------
lib/librte_cryptodev/rte_cryptodev_vdev.h | 210 +++++++++++++++++
lib/librte_cryptodev/rte_cryptodev_version.map | 18 +-
test/test/test_cryptodev.c | 59 +++--
.../test/test_cryptodev_kasumi_hash_test_vectors.h | 25 --
test/test/test_cryptodev_kasumi_test_vectors.h | 36 +--
test/test/test_cryptodev_perf.c | 148 ++++--------
.../test/test_cryptodev_snow3g_hash_test_vectors.h | 22 --
test/test/test_cryptodev_snow3g_test_vectors.h | 32 ---
test/test/test_cryptodev_zuc_test_vectors.h | 61 +----
32 files changed, 565 insertions(+), 772 deletions(-)
create mode 100644 lib/librte_cryptodev/rte_cryptodev_pci.h
create mode 100644 lib/librte_cryptodev/rte_cryptodev_vdev.h
next reply other threads:[~2017-06-24 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 10:37 Pablo de Lara [this message]
2017-06-29 21:38 ` 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=20170624103746.44061-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).