* [dpdk-users] rte_eth_dev_start failing after rte_eth_dev_stop: ixgbe
@ 2016-04-22 13:02 Shawn Lewis
0 siblings, 0 replies; 2+ messages in thread
From: Shawn Lewis @ 2016-04-22 13:02 UTC (permalink / raw)
To: users
Hello,
I am seeing strange behavior I haven't seen on some other other drivers.
When using the ixgbe driver with an I540 10Gb interface we see this
problem.
We have the traditional callback function:
kni_config_network_interface
Which gets called as interface is brought up/down. Within that function it
will execute a stop/start of the rte_eth_dev_start / rte_eth_dev_stop.
The issue we see is once the ixgbe device is EVER stopped, when calling
start we get the following errors:
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst
size no less than 4 (port=0).
PMD: ixgbe_alloc_rx_queue_mbufs(): RX mbuf alloc failed queue_id=0
PMD: ixgbe_dev_rx_queue_start(): Could not alloc mbuf for queue:0
PMD: ixgbe_dev_start(): Unable to start rxtx queues
PMD: ixgbe_dev_start(): failure in ixgbe_dev_start(): -1
APP: Failed to start port 0
Is this a known issue/bug/workaround (I can comment out all the start/stop
but that defeats the purpose).
Shawn
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-users] rte_eth_dev_start failing after rte_eth_dev_stop: ixgbe
@ 2016-08-04 16:00 Ori Zakin
0 siblings, 0 replies; 2+ messages in thread
From: Ori Zakin @ 2016-08-04 16:00 UTC (permalink / raw)
To: Shawn Lewis, users
Hi,
If still relevant, I posted two possible workarounds for this on the dpdk-dev list, see link below.
http://dpdk.org/ml/archives/dev/2016-August/045096.html
Ori Zakin
Hello,
I am seeing strange behavior I haven't seen on some other other drivers.
When using the ixgbe driver with an I540 10Gb interface we see this
problem.
We have the traditional callback function:
kni_config_network_interface
Which gets called as interface is brought up/down. Within that function it
will execute a stop/start of the rte_eth_dev_start / rte_eth_dev_stop.
The issue we see is once the ixgbe device is EVER stopped, when calling
start we get the following errors:
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst
size no less than 4 (port=0).
PMD: ixgbe_alloc_rx_queue_mbufs(): RX mbuf alloc failed queue_id=0
PMD: ixgbe_dev_rx_queue_start(): Could not alloc mbuf for queue:0
PMD: ixgbe_dev_start(): Unable to start rxtx queues
PMD: ixgbe_dev_start(): failure in ixgbe_dev_start(): -1
APP: Failed to start port 0
Is this a known issue/bug/workaround (I can comment out all the start/stop
but that defeats the purpose).
Shawn
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-08-04 16:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-22 13:02 [dpdk-users] rte_eth_dev_start failing after rte_eth_dev_stop: ixgbe Shawn Lewis
2016-08-04 16:00 Ori Zakin
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).