From: Akhil Goyal <akhil.goyal@nxp.com>
To: <dev@dpdk.org>
Cc: <hemant.agrawal@nxp.com>, <pablo.de.lara.guarch@intel.com>,
<declan.doherty@intel.com>, Akhil Goyal <akhil.goyal@nxp.com>
Subject: [dpdk-dev] [PATCH v2] doc: add missing devices in test-crypto-perf
Date: Wed, 12 Jul 2017 20:42:40 +0530 [thread overview]
Message-ID: <20170712151240.3424-1-akhil.goyal@nxp.com> (raw)
In-Reply-To: <20170712123441.2942-2-akhil.goyal@nxp.com>
crypto_armv8, crypto_scheduler and crypto_dpaa2_sec
are added in the documentation
Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
---
changes in v2:
added crypto_armv8 and crypto_scheduler
doc/guides/tools/cryptoperf.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf.rst
index 075a2bc..457f817 100644
--- a/doc/guides/tools/cryptoperf.rst
+++ b/doc/guides/tools/cryptoperf.rst
@@ -186,6 +186,9 @@ The following are the appication command-line options:
crypto_snow3g
crypto_kasumi
crypto_zuc
+ crypto_dpaa2_sec
+ crypto_armv8
+ crypto_scheduler
* ``--optype <name>``
--
2.9.3
next prev parent reply other threads:[~2017-07-12 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 12:34 [dpdk-dev] [PATCH] crypto/dpaa2_sec: fix typo error in comments Akhil Goyal
2017-07-12 12:34 ` [dpdk-dev] [PATCH] doc: add dpaa2-sec in test-crypto-perf Akhil Goyal
2017-07-12 12:43 ` De Lara Guarch, Pablo
2017-07-12 15:12 ` Akhil Goyal [this message]
2017-07-12 16:17 ` [dpdk-dev] [PATCH v2] doc: add missing devices " De Lara Guarch, Pablo
2017-07-13 15:50 ` De Lara Guarch, Pablo
2017-07-12 12:34 ` [dpdk-dev] [PATCH] crypto/dpaa2_sec: fix the incorrect free usage for dpsec Akhil Goyal
2017-07-12 14:46 ` De Lara Guarch, Pablo
2017-07-12 14:47 ` [dpdk-dev] [PATCH] crypto/dpaa2_sec: fix typo error in comments 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=20170712151240.3424-1-akhil.goyal@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=pablo.de.lara.guarch@intel.com \
/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).