From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net
Subject: [dpdk-dev] [PATCH 2/3] doc: fix coremask option for eventdev pipeline
Date: Mon, 16 Nov 2020 11:06:17 +0100
Message-ID: <20201116100618.2894-2-david.marchand@redhat.com> (raw)
In-Reply-To: <20201116100618.2894-1-david.marchand@redhat.com>
-w option in this context is an application option for coremask.
Restore it.
Fixes: db27370b5720 ("eal: replace blacklist/whitelist options")
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
doc/guides/sample_app_ug/eventdev_pipeline.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guides/sample_app_ug/eventdev_pipeline.rst b/doc/guides/sample_app_ug/eventdev_pipeline.rst
index 41ee8b7ee3..4508c3dcc8 100644
--- a/doc/guides/sample_app_ug/eventdev_pipeline.rst
+++ b/doc/guides/sample_app_ug/eventdev_pipeline.rst
@@ -47,7 +47,7 @@ these settings is shown below:
.. code-block:: console
./<build_dir>/examples/dpdk-eventdev_pipeline --vdev event_sw0 -- -r1 -t1 \
- -e4 -a FF00 -s4 -n0 -c32 -W1000 -D
+ -e4 -w FF00 -s4 -n0 -c32 -W1000 -D
The application has some sanity checking built-in, so if there is a function
(e.g.; the RX core) which doesn't have a cpu core mask assigned, the application
--
2.23.0
next prev parent reply other threads:[~2020-11-16 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 10:06 [dpdk-dev] [PATCH 1/3] test/eal: remove unneeded command David Marchand
2020-11-16 10:06 ` David Marchand [this message]
2020-11-19 18:47 ` [dpdk-dev] [PATCH 2/3] doc: fix coremask option for eventdev pipeline Thomas Monjalon
2020-11-16 10:06 ` [dpdk-dev] [PATCH 3/3] bus/vdev: fix comment David Marchand
2020-11-19 18:48 ` Thomas Monjalon
2020-11-19 18:50 ` [dpdk-dev] [PATCH 1/3] test/eal: remove unneeded command Thomas Monjalon
2020-11-20 9:00 ` David Marchand
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=20201116100618.2894-2-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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
DPDK patches and discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
dev@dpdk.org
public-inbox-index dev
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://inbox.dpdk.org/inbox.dpdk.dev
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git