From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 436] rte_eth_promiscuous_enable fails for memif on l2fwd
Date: Sat, 04 Apr 2020 02:34:16 +0000 [thread overview]
Message-ID: <bug-436-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=436
Bug ID: 436
Summary: rte_eth_promiscuous_enable fails for memif on l2fwd
Product: DPDK
Version: 20.02
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
target:
Application: l2fwd
CMD: `./build/l2fwd --vdev=net_tap0 --vdev=net_memif,role=master -l 8,51
--socket-mem=128,0 --socket-limit=1024,0 --file-prefix=1 --proc-type=primary
--no-pci -- -p 0x3 -T 1`
Error: `EAL: Error - exiting with code: 1
Cause: rte_eth_promiscuous_enable:err=Operation not supported, port=1`
Possible reason: in file `"rte_eth_memif.c"` for ` struct eth_dev_ops ops`,
absence of ".promiscuous_enable & .promiscuous_disable"
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-04-04 2:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-436-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).