Initializing and starting port on primary but transmitting on secondary I get port not ready

Stephen Hemminger stephen at networkplumber.org
Thu Sep 1 03:25:46 CEST 2022


On Wed, 31 Aug 2022 22:59:56 +0200
Anna Tauzzi <admin at argonnetech.net> wrote:

> I initialize a port with the following methods on a primary process:
> 
> rte_dev_probe(vf)
> 
> rte_eth_dev_configure(port_id, ... );
> 
> rte_eth_dev_adjust_nb_rx_tx_desc(port_id, ... );
> 
> rte_eth_rx_queue_setup(port_id, .... );
> 
> rte_eth_tx_queue_setup(port_id, ... );
> 
> rte_eth_dev_start(port_id ... );
> 
> 
> 
> Then I use the rte_eth_tx_burst(port_id) in the secondary process but I get
> this message:
> 
> called tx_pkt_burst for not ready port 0
> 
> Is this expected?

No looks like a device driver bug. Which PMD?


More information about the users mailing list