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 0/3] Crypto performance improvements
Date: Fri, 3 Mar 2017 16:12:35 +0000 [thread overview]
Message-ID: <1488557558-46085-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
With this patchset, user will be able to run performance tests
on different buffer and burst sizes, in a single run, instead
of having to run the application several times.
Also, the verify option has been removed and, instead,
a new verify test has been created, to simplify the throughput
and latency tests.
Pablo de Lara (2):
app/crypto-perf: do not append digest if not used
app/crypto-perf: add range/list of sizes
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 | 34 +-
app/test-crypto-perf/cperf_options_parsing.c | 252 ++++++++--
app/test-crypto-perf/cperf_test_latency.c | 517 ++++++++------------
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 | 576 +++++++++++++++++++++++
app/test-crypto-perf/cperf_test_verify.h | 58 +++
app/test-crypto-perf/cperf_verify_parser.c | 4 +-
app/test-crypto-perf/main.c | 59 ++-
doc/guides/tools/cryptoperf.rst | 27 +-
14 files changed, 1314 insertions(+), 761 deletions(-)
create mode 100644 app/test-crypto-perf/cperf_test_verify.c
create mode 100644 app/test-crypto-perf/cperf_test_verify.h
--
2.7.4
reply other threads:[~2017-03-03 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1488557558-46085-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).