All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Wiles <keith.wiles@intel.com>
To: dev@dpdk.org
Subject: [PATCH 09/11] doc/cryptoperf: use corelist instead of coremask
Date: Thu,  9 Feb 2017 12:14:48 -0600	[thread overview]
Message-ID: <20170209181450.58466-10-keith.wiles@intel.com> (raw)
In-Reply-To: <20170209181450.58466-1-keith.wiles@intel.com>

Signed-off-by: Keith Wiles <keith.wiles@intel.com>
---
 doc/guides/tools/cryptoperf.rst | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf.rst
index 6832312..30994cd 100644
--- a/doc/guides/tools/cryptoperf.rst
+++ b/doc/guides/tools/cryptoperf.rst
@@ -94,9 +94,10 @@ The following are the EAL command-line options that can be used in conjunction
 with the ``dpdk-test-crypto-perf`` applcation.
 See the DPDK Getting Started Guides for more information on these options.
 
-*   ``-c <COREMASK>``
+*   ``-c <COREMASK>`` or ``-l <CORELIST>``
 
-        Set the hexadecimal bitmask of the cores to run on.
+        Set the hexadecimal bitmask of the cores to run on. The corelist is a
+        list cores to use.
 
 *   ``-w <PCI>``
 
-- 
2.8.0.GIT

  parent reply	other threads:[~2017-02-09 18:15 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 18:14 [PATCH 00/11] moving away from coremask to corelist Keith Wiles
2017-02-09 18:14 ` [PATCH 01/11] doc/cryptodev: use corelist instead of coremask Keith Wiles
2017-02-09 18:14 ` [PATCH 02/11] doc/faq: " Keith Wiles
2017-02-09 18:14 ` [PATCH 03/11] doc/freebsd: " Keith Wiles
2017-02-09 18:14 ` [PATCH 04/11] doc/howto: " Keith Wiles
2017-02-09 23:00   ` Igor Ryzhov
2017-02-09 23:20     ` Wiles, Keith
2017-02-09 18:14 ` [PATCH 05/11] doc/linux: " Keith Wiles
2017-02-09 18:14 ` [PATCH 06/11] doc/nics: " Keith Wiles
2017-02-09 18:14 ` [PATCH 07/11] doc/prog_guide: " Keith Wiles
2017-02-09 18:14 ` [PATCH 08/11] doc/testpmd: " Keith Wiles
2017-02-09 18:14 ` Keith Wiles [this message]
2017-02-09 18:14 ` [PATCH 10/11] doc/xen: " Keith Wiles
2017-02-09 18:14 ` [PATCH 11/11] doc/sample_app: " Keith Wiles
2017-02-09 23:42 ` [PATCH v2 00/11] moving away from coremask to corelist Keith Wiles
2017-02-10  8:46   ` Thomas Monjalon
2017-02-10 13:47     ` Wiles, Keith
2017-02-09 23:42 ` [PATCH v2 01/11] doc/cryptodev: use corelist instead of coremask Keith Wiles
2017-02-09 23:42 ` [PATCH v2 02/11] doc/faq: " Keith Wiles
2017-02-09 23:42 ` [PATCH v2 03/11] doc/freebsd: " Keith Wiles
2017-02-09 23:42 ` [PATCH v2 04/11] doc/howto: " Keith Wiles
2017-02-09 23:42 ` [PATCH v2 05/11] doc/linux: " Keith Wiles
2017-02-09 23:42 ` [PATCH v2 06/11] doc/nics: " Keith Wiles
2017-02-09 23:42 ` [PATCH v2 07/11] doc/prog_guide: " Keith Wiles
2017-02-09 23:42 ` [PATCH v2 08/11] doc/testpmd: " Keith Wiles
2017-02-09 23:42 ` [PATCH v2 09/11] doc/cryptoperf: " Keith Wiles
2017-02-09 23:42 ` [PATCH v2 10/11] doc/xen: " Keith Wiles
2017-02-09 23:42 ` [PATCH v2 11/11] doc/sample_app: " Keith Wiles
2017-02-10 14:01 ` [PATCH v3] doc: " Keith Wiles
2017-02-21 15:53   ` Mcnamara, John
2017-02-21 17:38 ` [PATCH v4] " Keith Wiles
2017-02-22 10:20   ` Mcnamara, John
2017-02-27 19:13 ` [PATCH v5] " Keith Wiles
2017-02-28 17:14   ` Mcnamara, John
2017-03-01 19:40     ` Thomas Monjalon
2017-03-01 20:03       ` Wiles, Keith

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=20170209181450.58466-10-keith.wiles@intel.com \
    --to=keith.wiles@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.