Bug 43 - "rte_eth_tx_queue_setup" will be failed if argument "tx_conf" not specified
Summary: "rte_eth_tx_queue_setup" will be failed if argument "tx_conf" not specified
Status: CONFIRMED
Alias: None
Product: DPDK
Classification: Unclassified
Component: ethdev (show other bugs)
Version: 18.05
Hardware: x86 Linux
: Normal normal
Target Milestone: ---
Assignee: dev
URL:
Depends on:
Blocks:
 
Reported: 2018-05-09 09:57 CEST by Liu Hongbo
Modified: 2020-03-03 13:16 CET (History)
2 users (show)



Attachments

Description Liu Hongbo 2018-05-09 09:57:39 CEST
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?
Comment 1 beilei.xing 2018-09-30 07:45:53 CEST
have some questions:
1. what's the device ID?
2. do you changed l2fwd.cli?
3. what's your topology?
Comment 2 Muhammad Ahmad 2020-03-03 13:16:51 CET
ETH_TXQ_FLAGS_NO* API is removed in 18.08, as described in /doc/guides/rel_notes/release_18.08.rst

18.05 is not LTS, is there still a need to fix this bug?

Note You need to log in before you can comment on or make changes to this bug.