From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 43] "rte_eth_tx_queue_setup" will be failed to called if argument "tx_conf" not specified
Date: Wed, 09 May 2018 07:57:39 +0000 [thread overview]
Message-ID: <bug-43-3@http.dpdk.org/tracker/> (raw)
https://dpdk.org/tracker/show_bug.cgi?id=43
Bug ID: 43
Summary: "rte_eth_tx_queue_setup" will be failed to called if
argument "tx_conf" not specified
Product: DPDK
Version: 18.05
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: cnliuhb@gmail.com
Target Milestone: ---
OS: Ubuntu 16.04 x86_64 in virtualbox
interfaces:
0000:00:08.0 '82540EM Gigabit Ethernet Controller 100e' drv=igb_uio
unused=e1000,uio_pci_generic
0000:00:09.0 '82540EM Gigabit Ethernet Controller 100e' drv=igb_uio
unused=e1000,uio_pci_generic
When start "./build/app/ip_pipeline -l 0-3 -n 1 -- -s ./examples/l2fwd.cli", it
will be failed to add link, and reports the error:
eth_em_tx_queue_setup(): 0x5f6f6c0: Tx queue offloads 0x801d don't match
port offloads 0x0 or supported port offloads 0xf or supported queue offloads
0xf
Command "link" failed.
The reason is at rte_ethdev.c line 1610, it will set full tx offloads in
function "rte_eth_convert_txq_flags" if default_txconf.txq_flags is 0, which is
wrong.
One proper fix way is driver should set proper "ETH_TXQ_FLAGS_NOXXXX" flags to
default_txconf.txq_flags.
Any idea?
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-05-09 7:57 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-43-3@http.dpdk.org/tracker/ \
--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).