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 18.05-rc5
Date: Tue, 22 May 2018 15:38:48 +0100 [thread overview]
Message-ID: <20180522143848.6559-1-pablo.de.lara.guarch@intel.com> (raw)
The following changes since commit 3291abb5a2a5f24c109ab74e6aad0545927333a7:
ethdev: fix type and scope of variables in Rx burst (2018-05-22 16:32:36 +0200)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-crypto
for you to fetch changes up to bbabaddd854f858477df32e7882ba848bd33317d:
doc/crypto: update ZUC installation section (2018-05-22 15:36:12 +0100)
----------------------------------------------------------------
Fan Zhang (1):
crypto/scheduler: fix possible duplicated ring names
Fiona Trahe (4):
doc/crypto: add clarification about chained mbuf feature
compressdev: clarify buffer size limitation
compressdev: clarify when private xform can be cleared
cryptodev: clarify when session can be cleared
Jerin Jacob (2):
app/crypto-perf: use strcpy for allocated string
app/crypto-perf: fix memcpy source
Kamil Chalupnik (1):
app/bbdev: fix unchecked return value
Kirill Rybalchenko (2):
crypto/scheduler: fix multicore rings re-use
crypto/scheduler: fix 64-bit mask of workers cores
Pablo de Lara (16):
crypto/aesni_mb: fix capabilities
crypto/aesni_gcm: remove unneeded cast
cryptodev: fix supported size check
cryptodev: extend feature flags description
cryptodev: add missing feature string
compressdev: remove unused driver id
compressdev: clarify mbuf offsets
doc: announce ABI change for crypto sym info struct
doc: announce ABI change for crypto info struct
doc: announce deprecation for attach/detach crypto session
doc: announce deprecation in crypto queue pair start/stop
doc: announce deprecation in crypto feature flags
cryptodev: rename get session size API
doc/crypto: update KASUMI installation section
doc/crypto: update SNOW3G installation section
doc/crypto: update ZUC installation section
app/test-bbdev/test_bbdev_perf.c | 8 ++-
app/test-crypto-perf/cperf_test_vector_parsing.c | 7 +--
app/test-crypto-perf/main.c | 2 +-
doc/guides/cryptodevs/kasumi.rst | 10 ++--
doc/guides/cryptodevs/overview.rst | 10 ++++
doc/guides/cryptodevs/snow3g.rst | 10 ++--
doc/guides/cryptodevs/zuc.rst | 10 ++--
doc/guides/prog_guide/cryptodev_lib.rst | 6 +-
doc/guides/rel_notes/deprecation.rst | 25 ++++++++
drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 4 +-
drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 2 +-
drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 23 +++++++-
drivers/crypto/armv8/rte_armv8_pmd.c | 2 +-
drivers/crypto/kasumi/rte_kasumi_pmd.c | 2 +-
drivers/crypto/openssl/rte_openssl_pmd.c | 2 +-
drivers/crypto/scheduler/rte_cryptodev_scheduler.h | 2 +-
drivers/crypto/scheduler/scheduler_multicore.c | 38 ++++++++----
drivers/crypto/scheduler/scheduler_pmd.c | 68 +++++++++++++++++-----
drivers/crypto/scheduler/scheduler_pmd_private.h | 2 +-
drivers/crypto/snow3g/rte_snow3g_pmd.c | 2 +-
drivers/crypto/zuc/rte_zuc_pmd.c | 2 +-
examples/ipsec-secgw/ipsec-secgw.c | 2 +-
examples/ipsec-secgw/ipsec.c | 12 ----
examples/l2fwd-crypto/main.c | 2 +-
examples/vhost_crypto/main.c | 2 +-
lib/librte_compressdev/rte_comp.h | 18 +++++-
lib/librte_compressdev/rte_compressdev.h | 3 +-
lib/librte_compressdev/rte_compressdev_internal.h | 3 -
lib/librte_cryptodev/rte_cryptodev.c | 59 +++++++++++++++----
lib/librte_cryptodev/rte_cryptodev.h | 44 +++++++++++++-
lib/librte_cryptodev/rte_cryptodev_version.map | 8 +++
test/test/test_cryptodev.c | 8 ++-
test/test/test_event_crypto_adapter.c | 2 +-
33 files changed, 294 insertions(+), 106 deletions(-)
next reply other threads:[~2018-05-22 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 14:38 Pablo de Lara [this message]
2018-05-22 17:36 ` 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=20180522143848.6559-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).