[dpdk-dev,4/4] doc: document new pmd-cyclecount benchmarking mode in test-crypto-perf
Checks
Commit Message
Also, document the new pmd-cyclecount-specific flag.
Signed-off-by: Burakov, Anatoly <anatoly.burakov@intel.com>
---
doc/guides/rel_notes/release_17_11.rst | 6 ++++++
doc/guides/tools/cryptoperf.rst | 10 +++++++++-
2 files changed, 15 insertions(+), 1 deletion(-)
Comments
> -----Original Message-----
> From: Burakov, Anatoly
> Sent: Thursday, August 24, 2017 11:48 AM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Doherty,
> Declan <declan.doherty@intel.com>; Burakov, Anatoly
> <anatoly.burakov@intel.com>
> Subject: [PATCH 4/4] doc: document new pmd-cyclecount benchmarking
> mode in test-crypto-perf
>
> Also, document the new pmd-cyclecount-specific flag.
As said with patch 2, I would merge this patch with patch number of 3.
>
> Signed-off-by: Burakov, Anatoly <anatoly.burakov@intel.com>
> ---
> doc/guides/rel_notes/release_17_11.rst | 6 ++++++
> doc/guides/tools/cryptoperf.rst | 10 +++++++++-
> 2 files changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/rel_notes/release_17_11.rst
> b/doc/guides/rel_notes/release_17_11.rst
> index 170f4f9..860858c 100644
> --- a/doc/guides/rel_notes/release_17_11.rst
> +++ b/doc/guides/rel_notes/release_17_11.rst
> @@ -41,6 +41,12 @@ New Features
> Also, make sure to start the actual text at the margin.
>
> =========================================================
>
> +* **Add new benchmarking mode to dpdk-crypto-perf-test application.**
Name of the app is "dpdk-test-crypto-perf (above and below).
> +
> + Added new "PMD cyclecount" benchmark mode to dpdk-crypto-perf-test
> + application that displays more detailed breakdown of CPU cycles used
> + by hardware acceleration.
> +
>
@@ -41,6 +41,12 @@ New Features
Also, make sure to start the actual text at the margin.
=========================================================
+* **Add new benchmarking mode to dpdk-crypto-perf-test application.**
+
+ Added new "PMD cyclecount" benchmark mode to dpdk-crypto-perf-test application
+ that displays more detailed breakdown of CPU cycles used by hardware
+ acceleration.
+
Resolved Issues
---------------
@@ -50,7 +50,8 @@ offload are still consumed by the test tool and included in the cycle-count.
These cycles are consumed by retries and inefficient API calls enqueuing and
dequeuing smaller bursts than specified by the cmdline parameter. This results
in a larger cycle-count measurement and should not be interpreted as an offload
-cost measurement.
+cost measurement. Using "pmd-cyclecount" mode will give a better idea of
+actual costs of hardware acceleration.
On hardware devices the throughput measurement is not necessarily the maximum
possible for the device, e.g. it may be necessary to use multiple cores to keep
@@ -134,6 +135,7 @@ The following are the appication command-line options:
throughput
latency
verify
+ pmd-cyclecount
* ``--silent``
@@ -329,6 +331,12 @@ The following are the appication command-line options:
Set default number of descriptors in cryptodev.
+* ``--pmd-cyclecount-delay-ms <n>``
+
+ Add a delay (in milliseconds) between enqueue and dequeue in
+ pmd-cyclecount benchmarking mode (useful when benchmarking
+ hardware acceleration).
+
* ``--csv-friendly``
Enable test result output CSV friendly rather than human friendly.