From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/4] doc: document new nb-desc parameter for test-crypto-perf app
Date: Mon, 4 Sep 2017 13:12:07 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC1516D@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <5333960e82770fd1fc5d0441767922b5aa8c31e3.1503566892.git.anatoly.burakov@intel.com>
> -----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 2/4] doc: document new nb-desc parameter for test-
> crypto-perf app
Since this is related to the previous patch and it is a small addition,
merge it with the previous patch.
>
> Signed-off-by: Burakov, Anatoly <anatoly.burakov@intel.com>
> ---
> doc/guides/tools/cryptoperf.rst | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/doc/guides/tools/cryptoperf.rst
> b/doc/guides/tools/cryptoperf.rst index 457f817..985848b 100644
> --- a/doc/guides/tools/cryptoperf.rst
> +++ b/doc/guides/tools/cryptoperf.rst
> @@ -325,6 +325,10 @@ The following are the appication command-line
> options:
>
> Set the size of digest.
>
> +* ``--desc-nb <n>``
> +
> + Set default number of descriptors in cryptodev.
I think this should be reworded, as it is not setting the default number of descriptor (which is 2048),
but it is setting the number of descriptors for each crypto device.
> +
> * ``--csv-friendly``
>
> Enable test result output CSV friendly rather than human friendly.
> --
> 2.7.4
next prev parent reply other threads:[~2017-09-04 13:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 10:48 [dpdk-dev] [PATCH 0/4] New crypto acceleration benchmark mode Anatoly Burakov
2017-08-24 10:48 ` [dpdk-dev] [PATCH 1/4] test-crypto-perf: add nb-desc parameter Anatoly Burakov
2017-09-04 13:09 ` De Lara Guarch, Pablo
2017-08-24 10:48 ` [dpdk-dev] [PATCH 2/4] doc: document new nb-desc parameter for test-crypto-perf app Anatoly Burakov
2017-09-04 13:12 ` De Lara Guarch, Pablo [this message]
2017-08-24 10:48 ` [dpdk-dev] [PATCH 3/4] test-crypto-perf: add new PMD benchmarking mode Anatoly Burakov
2017-09-04 14:24 ` De Lara Guarch, Pablo
2017-09-04 14:26 ` De Lara Guarch, Pablo
2017-08-24 10:48 ` [dpdk-dev] [PATCH 4/4] doc: document new pmd-cyclecount benchmarking mode in test-crypto-perf Anatoly Burakov
2017-09-04 14:28 ` De Lara Guarch, Pablo
2017-09-12 9:36 ` [dpdk-dev] [PATCH v2 0/2] New crypto acceleration benchmark mode Anatoly Burakov
2017-09-12 9:36 ` [dpdk-dev] [PATCH v2 1/2] app/crypto-perf: add nb-desc parameter Anatoly Burakov
2017-09-18 9:39 ` De Lara Guarch, Pablo
2017-09-12 9:36 ` [dpdk-dev] [PATCH v2 2/2] app/crypto-perf: add new PMD benchmarking mode Anatoly Burakov
2017-09-18 14:05 ` De Lara Guarch, Pablo
2017-09-20 14:04 ` [dpdk-dev] [PATCH v2 0/2] New crypto acceleration benchmark mode 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=E115CCD9D858EF4F90C690B0DCB4D8976CC1516D@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=anatoly.burakov@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).