> -----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.gua...@intel.com>; Doherty,
> Declan <declan.dohe...@intel.com>; Burakov, Anatoly
> <anatoly.bura...@intel.com>
> Subject: [PATCH 3/4] test-crypto-perf: add new PMD benchmarking mode
>
> This patch adds a new benchmarking mode, which is intended for
> microbenchmarking individual parts of the cryptodev framework,
> specifically crypto ops alloc-build-free, cryptodev PMD enqueue and
> cryptodev PMD dequeue.
>
> It works by first benchmarking crypto operation alloc-build-free loop (no
> enqueues/dequeues happening), and then benchmarking enqueue and
> dequeue separately, by first completely filling up the TX queue, and then
> completely draining the RX queue.
>
> Results are shown as cycle counts per alloc/build/free, PMD enqueue and
> PMD dequeue.
>
> One new test mode is added: "pmd-cyclecount"
> (called with --ptest=pmd-cyclecount)
>
> New command-line argument is also added:
> --pmd-cyclecount-delay-ms: this is a pmd-cyclecount-specific parameter
> that controls the delay between enqueue and dequeue. This is
> useful for benchmarking hardware acceleration, as hardware may
> not be able to keep up with enqueued packets. This parameter
> can be increased if there are large amounts of dequeue
> retries.
>
> Signed-off-by: Burakov, Anatoly <anatoly.bura...@intel.com>
...
> diff --git a/app/test-crypto-perf/cperf_options_parsing.c b/app/test-crypto-
> perf/cperf_options_parsing.c
> index f4097d9..42a920f 100644
> --- a/app/test-crypto-perf/cperf_options_parsing.c
> +++ b/app/test-crypto-perf/cperf_options_parsing.c
...
> static int
> @@ -782,6 +804,7 @@ cperf_opts_parse_long(int opt_idx, struct
> cperf_options *opts)
> { CPERF_AEAD_AAD_SZ, parse_aead_aad_sz },
> { CPERF_DIGEST_SZ, parse_digest_sz },
> { CPERF_CSV, parse_csv_friendly},
> + { CPERF_PMD_CYCLECOUNT_DELAY_MS,
> parse_pmd_cyclecount_delay_ms},
Sorry, I missed this one in the previous email.
To have a consistent alignment, could you make the name of this macro shorter?
Thanks,
Pablo
