From: Akhil Goyal <akhil.goyal@nxp.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-crypto 19.11 rc3
Date: Wed, 20 Nov 2019 17:08:34 +0530 [thread overview]
Message-ID: <20191120113834.24323-1-akhil.goyal@nxp.com> (raw)
The following changes since commit 3be76aa9294f3788b4f9c615642e6027f1b7948a:
ci: add 32-bit travis builds (2019-11-19 22:23:31 +0100)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-crypto
for you to fetch changes up to 539b74b9d8e8567f4679c118951f0fc025b9c717:
crypto/openssl: support SG for inplace buffers (2019-11-20 17:05:51 +0530)
----------------------------------------------------------------
Akhil Goyal (2):
app/test-crypto-perf: support PDCP
crypto/openssl: support SG for inplace buffers
Fan Zhang (1):
examples/fips_validation: fix auth verify
Lukasz Bartosik (1):
examples/ipsec-secgw: fix default configuration
Pablo de Lara (1):
doc: update release notes for AESNI PMDs
Stephen Hemminger (1):
examples/ipsec-segw: add SPDX license tag
app/test-crypto-perf/cperf_ops.c | 117 ++++++++++++++++++++-
app/test-crypto-perf/cperf_options.h | 15 ++-
app/test-crypto-perf/cperf_options_parsing.c | 73 +++++++++++++
app/test-crypto-perf/cperf_test_common.c | 1 +
app/test-crypto-perf/cperf_test_throughput.c | 24 +++--
app/test-crypto-perf/cperf_test_vectors.c | 55 ++++++++++
app/test-crypto-perf/main.c | 3 +-
app/test-crypto-perf/meson.build | 2 +-
app/test/test_cryptodev_aes_test_vectors.h | 2 +
doc/guides/cryptodevs/features/openssl.ini | 1 +
doc/guides/rel_notes/release_19_11.rst | 11 +-
doc/guides/tools/cryptoperf.rst | 10 ++
drivers/crypto/openssl/rte_openssl_pmd.c | 84 +++++++++++----
examples/fips_validation/main.c | 58 +++-------
examples/ipsec-secgw/ep0.cfg | 8 +-
examples/ipsec-secgw/ep1.cfg | 12 +--
examples/ipsec-secgw/test/bypass_defs.sh | 1 +
examples/ipsec-secgw/test/common_defs.sh | 1 +
examples/ipsec-secgw/test/common_defs_secgw.sh | 1 +
examples/ipsec-secgw/test/data_rxtx.sh | 1 +
examples/ipsec-secgw/test/linux_test4.sh | 1 +
examples/ipsec-secgw/test/linux_test6.sh | 1 +
examples/ipsec-secgw/test/pkttest.py | 1 +
examples/ipsec-secgw/test/pkttest.sh | 1 +
examples/ipsec-secgw/test/run_test.sh | 1 +
.../test/trs_3descbc_sha1_common_defs.sh | 1 +
examples/ipsec-secgw/test/trs_3descbc_sha1_defs.sh | 1 +
.../test/trs_3descbc_sha1_esn_atom_defs.sh | 1 +
.../ipsec-secgw/test/trs_3descbc_sha1_esn_defs.sh | 1 +
.../ipsec-secgw/test/trs_3descbc_sha1_old_defs.sh | 1 +
.../test/trs_aescbc_sha1_common_defs.sh | 1 +
examples/ipsec-secgw/test/trs_aescbc_sha1_defs.sh | 1 +
.../test/trs_aescbc_sha1_esn_atom_defs.sh | 1 +
.../ipsec-secgw/test/trs_aescbc_sha1_esn_defs.sh | 1 +
.../ipsec-secgw/test/trs_aescbc_sha1_old_defs.sh | 1 +
.../test/trs_aesctr_sha1_common_defs.sh | 1 +
examples/ipsec-secgw/test/trs_aesctr_sha1_defs.sh | 1 +
.../test/trs_aesctr_sha1_esn_atom_defs.sh | 1 +
.../ipsec-secgw/test/trs_aesctr_sha1_esn_defs.sh | 1 +
.../ipsec-secgw/test/trs_aesctr_sha1_old_defs.sh | 1 +
.../ipsec-secgw/test/trs_aesgcm_common_defs.sh | 1 +
examples/ipsec-secgw/test/trs_aesgcm_defs.sh | 1 +
.../ipsec-secgw/test/trs_aesgcm_esn_atom_defs.sh | 1 +
examples/ipsec-secgw/test/trs_aesgcm_esn_defs.sh | 1 +
.../test/trs_aesgcm_inline_crypto_defs.sh | 1 +
.../test/trs_aesgcm_inline_crypto_old_defs.sh | 1 +
examples/ipsec-secgw/test/trs_aesgcm_old_defs.sh | 1 +
examples/ipsec-secgw/test/trs_ipv6opts.py | 1 +
.../test/tun_3descbc_sha1_common_defs.sh | 1 +
examples/ipsec-secgw/test/tun_3descbc_sha1_defs.sh | 1 +
.../test/tun_3descbc_sha1_esn_atom_defs.sh | 1 +
.../ipsec-secgw/test/tun_3descbc_sha1_esn_defs.sh | 1 +
.../ipsec-secgw/test/tun_3descbc_sha1_old_defs.sh | 1 +
.../test/tun_aescbc_sha1_common_defs.sh | 1 +
examples/ipsec-secgw/test/tun_aescbc_sha1_defs.sh | 1 +
.../test/tun_aescbc_sha1_esn_atom_defs.sh | 1 +
.../ipsec-secgw/test/tun_aescbc_sha1_esn_defs.sh | 1 +
.../ipsec-secgw/test/tun_aescbc_sha1_old_defs.sh | 1 +
.../test/tun_aesctr_sha1_common_defs.sh | 1 +
examples/ipsec-secgw/test/tun_aesctr_sha1_defs.sh | 1 +
.../test/tun_aesctr_sha1_esn_atom_defs.sh | 1 +
.../ipsec-secgw/test/tun_aesctr_sha1_esn_defs.sh | 1 +
.../ipsec-secgw/test/tun_aesctr_sha1_old_defs.sh | 1 +
.../ipsec-secgw/test/tun_aesgcm_common_defs.sh | 1 +
examples/ipsec-secgw/test/tun_aesgcm_defs.sh | 1 +
.../ipsec-secgw/test/tun_aesgcm_esn_atom_defs.sh | 1 +
examples/ipsec-secgw/test/tun_aesgcm_esn_defs.sh | 1 +
.../test/tun_aesgcm_inline_crypto_defs.sh | 1 +
.../test/tun_aesgcm_inline_crypto_old_defs.sh | 1 +
examples/ipsec-secgw/test/tun_aesgcm_old_defs.sh | 1 +
70 files changed, 445 insertions(+), 85 deletions(-)
next reply other threads:[~2019-11-20 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 11:38 Akhil Goyal [this message]
2019-11-20 16:59 ` 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=20191120113834.24323-1-akhil.goyal@nxp.com \
--to=akhil.goyal@nxp.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).