Skip to contentSkip to conversation

"rte_eth_tx_queue_setup" will be failed to called if argument "tx_conf" not specified

Bug 43 [email protected] 1 participant 1 message May 9, 2018

lore
Share & tools
lore
#0 lore 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: [email protected]
Reporter: [email protected]
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?

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.