[dpdk-dev] [PATCH v2 0/2] New crypto acceleration benchmark mode

[De Lara Guarch, Pablo]

> -----Original Message-----
> From: Burakov, Anatoly
> Sent: Tuesday, September 12, 2017 10:36 AM
> To: dev at dpdk.org
> Cc: Doherty, Declan <declan.doherty at intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch at intel.com>
> Subject: [PATCH v2 0/2] New crypto acceleration benchmark mode
> 
> This patchset adds a new "PMD cyclecount" test mode for test-crypto-perf
> application. This mode is intended to measure hardware acceleration cost
> (in terms of cycle count) more accurately than throughput test.
> 
> The general idea is the following:
> - Measure build-alloc-free cycle separately
> - Alloc and build ops
> - Measure completely filling up the TX ring
> - Wait until ops are processed
> - Measure completely draining the RX ring
> - Free all allocated ops
> 
> In order to make measurements more accurate, the enqueue/dequeue is
> still done in bursts of specified size, but all of the bursts are now part of a
> "superburst" of size equal to number of descriptors configured for the
> device. So, if the number of descriptors configured was 2048 (the default),
> then 2048 ops will be enqueued and dequeued, in bursts of size specified by
> test command line.
> 
> The following command-line switch will run the test:
>   --ptest=pmd-cyclecount
> 
> In addition to a new mode, two mode command line switches are added:
> - --desc-nb - configure number of cryptodev descriptors. This value was
>          previously hardcoded to 2048, but is now configurable and set
>          to 2048 by default (so existing behavior is unchanged).
> - --pmd-cyclecount-delay-ms - pmd-cyclecount-specific parameter that
>          configures the delay (in milliseconds) between TX and RX
>          superbursts, to allow hardware to process ops. Set to 0 by
>          default, and it is expected that each user will tune it for
>          every device. This has no effect on other benchmark modes.
> 
> PMD cyclecount mode can be used to benchmark software cryptodev
> drivers as well, but the results will be far less accurate for smaller burst
> sizes.
> 
> v2: squashed documentation patches into relevant commits
>     fixed documentation
>     fixed commit messages
>     formatting and naming fixes
> 
> Anatoly Burakov (2):
>   app/crypto-perf: add nb-desc parameter
>   app/crypto-perf: add new PMD benchmarking mode
> 
>  app/test-crypto-perf/Makefile                    |   1 +
>  app/test-crypto-perf/cperf_options.h             |  10 +-
>  app/test-crypto-perf/cperf_options_parsing.c     |  54 ++
>  app/test-crypto-perf/cperf_test_pmd_cyclecount.c | 675
> +++++++++++++++++++++++  app/test-crypto-
> perf/cperf_test_pmd_cyclecount.h |  61 ++
>  app/test-crypto-perf/main.c                      |  11 +-
>  doc/guides/rel_notes/release_17_11.rst           |   6 +
>  doc/guides/tools/cryptoperf.rst                  |  14 +-
>  8 files changed, 828 insertions(+), 4 deletions(-)  create mode 100644
> app/test-crypto-perf/cperf_test_pmd_cyclecount.c
>  create mode 100644 app/test-crypto-perf/cperf_test_pmd_cyclecount.h
> 
> --
> 2.7.4

Applied to dpdk-next-crypto.

I think it will be a good idea to extend the documentation and explain more in detail
the different modes that the application offers, before the release is out.

Thanks,

Pablo