From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 392] l3fwd fails to run with eventdev
Date: Fri, 07 Feb 2020 03:29:58 +0000 [thread overview]
Message-ID: <bug-392-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=392
Bug ID: 392
Summary: l3fwd fails to run with eventdev
Product: DPDK
Version: 20.02
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
DPDK version: v20.02-rc2
example: l3fwd
Documentation: doc/guides/sample_app_ug/l3_forward.rst
cmd: `./build/l3fwd -l 4-7 -s 0-3 -n 4 --vdev event_sw0 -- -p 0x3
--mode=eventdev --eventq-sched=ordered`
Expected Result: Application should be running as per the documenation
Error:
```
EAL: Detected 88 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: invalid service coremask
Usage: ./build/l3fwd [options]
```
Reason: the service takes HEX value mask. `-s SERVICE COREMASK Hexadecimal
bitmask of cores to be used as service cores`
Working condition: ```./build/l3fwd -l 0-7 -s 0xf0000 -n 4 --vdev event_sw0 --
-p 0x3 --mode=eventdev --eventq-sched=ordered```
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-02-07 3:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 3:29 bugzilla [this message]
2020-02-07 10:20 ` bugzilla
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=bug-392-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).