From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] doc: added missing new EAL options in testpmd UG
Date: Fri, 27 Mar 2015 16:50:13 +0000 [thread overview]
Message-ID: <1427475013-16879-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
Added information on testpmd user guide
for -l, --lcores and --master-lcore options
Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
doc/guides/testpmd_app_ug/run_app.rst | 23 +++++++++++++++++++++++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/doc/guides/testpmd_app_ug/run_app.rst b/doc/guides/testpmd_app_ug/run_app.rst
index 3898e67..21e6c27 100644
--- a/doc/guides/testpmd_app_ug/run_app.rst
+++ b/doc/guides/testpmd_app_ug/run_app.rst
@@ -42,6 +42,29 @@ See the DPDK Getting Started Guide for more information on these options.
Set the hexadecimal bitmask of the cores to run on.
+* -l CORELIST
+
+ List of cores to run on
+
+ The argument format is <c1>[-c2][,c3[-c4],...]
+ where c1, c2, etc are core indexes between 0 and 128
+
+* --lcores COREMAP
+
+ Map lcore set to physical cpu set
+
+ The argument format is
+ '<lcores[@cpus]>[<,lcores[@cpus]>...]'
+ lcores and cpus list are grouped by '(' and ')'
+ Within the group, '-' is used for range separator,
+ ',' is used for single number separator.
+ '( )' can be omitted for single element group,
+ '@' can be omitted if cpus and lcores have the same value
+
+* --master-lcore ID
+
+ Core ID that is used as master
+
* -n NUM
Set the number of memory channels to use.
--
1.7.4.1
next reply other threads:[~2015-03-27 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 16:50 Pablo de Lara [this message]
2015-03-27 16:57 ` Butler, Siobhan A
2015-03-31 0:09 ` Thomas Monjalon
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=1427475013-16879-1-git-send-email-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@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).