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 v2 0/9] Crypto performance app improvements
Date: Mon, 27 Mar 2017 12:25:57 +0100 [thread overview]
Message-ID: <1490613966-74180-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
In-Reply-To: <1488557592-46193-1-git-send-email-pablo.de.lara.guarch@intel.com>
This patchset makes the following changes in the crypto-perf app:
- Adds the option to run performance tests on different
buffer and burst sizes, in a single run, instead of having to
run the application several times.
- Cleans up the application, by removing unused functions and
separating the verify option in a new test type
- Fixes several issues in the application (such as wrong test vectors)
Pablo de Lara (8):
app/crypto-perf: remove cyclecount test type
app/crypto-perf: remove unused file
app/crypto-perf: fix AES CBC 128 test vectors
app/crypto-perf: do not append digest if not used
app/crypto-perf: display results in test runner
app/crypto-perf: add range/list of sizes
app/crypto-perf: add extra option checks
app/crypto-perf: reorg options structure
Sergio Gonzalez Monroy (1):
app/crypto-perf: move verify as single test type
app/test-crypto-perf/Makefile | 1 +
app/test-crypto-perf/cperf_ops.c | 20 +-
app/test-crypto-perf/cperf_ops.h | 5 -
app/test-crypto-perf/cperf_options.h | 35 +-
app/test-crypto-perf/cperf_options_parsing.c | 308 ++++++++++--
app/test-crypto-perf/cperf_test_latency.c | 508 ++++++++------------
app/test-crypto-perf/cperf_test_throughput.c | 502 +++++++-------------
app/test-crypto-perf/cperf_test_vector_parsing.c | 12 +-
app/test-crypto-perf/cperf_test_vectors.c | 8 +-
app/test-crypto-perf/cperf_test_verify.c | 579 +++++++++++++++++++++++
app/test-crypto-perf/cperf_test_verify.h | 58 +++
app/test-crypto-perf/cperf_verify_parser.c | 314 ------------
app/test-crypto-perf/data/aes_cbc_128_sha.data | 439 +++++++++--------
app/test-crypto-perf/main.c | 71 ++-
doc/guides/tools/cryptoperf.rst | 27 +-
15 files changed, 1592 insertions(+), 1295 deletions(-)
create mode 100644 app/test-crypto-perf/cperf_test_verify.c
create mode 100644 app/test-crypto-perf/cperf_test_verify.h
delete mode 100644 app/test-crypto-perf/cperf_verify_parser.c
--
2.7.4
next prev parent reply other threads:[~2017-03-27 11:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 16:13 [dpdk-dev] [PATCH 0/3] " Pablo de Lara
2017-03-03 16:13 ` [dpdk-dev] [PATCH 1/3] app/crypto-perf: move verify as single test type Pablo de Lara
2017-03-03 16:13 ` [dpdk-dev] [PATCH 2/3] app/crypto-perf: do not append digest if not used Pablo de Lara
2017-03-03 16:13 ` [dpdk-dev] [PATCH 3/3] app/crypto-perf: add range/list of sizes Pablo de Lara
2017-03-27 11:25 ` Pablo de Lara [this message]
2017-03-27 11:25 ` [dpdk-dev] [PATCH v2 1/9] app/crypto-perf: remove cyclecount test type Pablo de Lara
2017-03-27 11:25 ` [dpdk-dev] [PATCH v2 2/9] app/crypto-perf: remove unused file Pablo de Lara
2017-03-27 11:26 ` [dpdk-dev] [PATCH v2 3/9] app/crypto-perf: fix AES CBC 128 test vectors Pablo de Lara
2017-03-27 11:26 ` [dpdk-dev] [PATCH v2 4/9] app/crypto-perf: move verify as single test type Pablo de Lara
2017-03-27 11:26 ` [dpdk-dev] [PATCH v2 5/9] app/crypto-perf: do not append digest if not used Pablo de Lara
2017-03-27 11:26 ` [dpdk-dev] [PATCH v2 6/9] app/crypto-perf: display results in test runner Pablo de Lara
2017-03-27 11:26 ` [dpdk-dev] [PATCH v2 7/9] app/crypto-perf: add range/list of sizes Pablo de Lara
2017-03-27 11:26 ` [dpdk-dev] [PATCH v2 8/9] app/crypto-perf: add extra option checks Pablo de Lara
2017-03-27 11:26 ` [dpdk-dev] [PATCH v2 9/9] app/crypto-perf: reorg options structure Pablo de Lara
2017-03-27 12:29 ` [dpdk-dev] [PATCH v2 0/9] Crypto performance app improvements De Lara Guarch, Pablo
2017-03-29 15:24 ` Sergio Gonzalez Monroy
2017-03-29 22:22 ` De Lara Guarch, Pablo
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=1490613966-74180-1-git-send-email-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).