* [dpdk-dev] em1000 driver lockup in KVM
@ 2016-07-22 21:19 Prabahar Radhakrishnan
2016-07-22 22:39 ` Stephen Hemminger
0 siblings, 1 reply; 2+ messages in thread
From: Prabahar Radhakrishnan @ 2016-07-22 21:19 UTC (permalink / raw)
To: users, dev
Hi,
I was running a dpdk application with e1000 driver and I am facing a
rare driver lockup condition. Under this condition, what I am seeing is
that the Receive side locks up. The transmit side is fine. When I execute
"rte_eth_dev_stop()/rte_eth_dev_start()" from within the VM, the dpdk
application recovers. The lockup happens once in 2 or 3 days if I
continuously ping an IP address serviced by the dpdk application. Once it
locks up, what I am noticing is that even though packets are coming in, the
driver is not populating them and signaling the event. In other words, in
"eth_em_recv_pkts" call, I am not seeing "E1000_RXD_STAT_DD" being set for
status, and the driver bails out. If anyone has come across such
condition, please let me know? Appreciate the help.
Environment: I have a VM running on top of Ubuntu/KVM.
Application: Running dpdk-2.0.0.
VM: uses e1000 driver.
On the KVM side, our port is sitting in a bridge. There are other VNFs
that we use for testing and some of them are using virtio driver.
Thank You
regards Prab
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-dev] em1000 driver lockup in KVM
2016-07-22 21:19 [dpdk-dev] em1000 driver lockup in KVM Prabahar Radhakrishnan
@ 2016-07-22 22:39 ` Stephen Hemminger
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2016-07-22 22:39 UTC (permalink / raw)
To: Prabahar Radhakrishnan; +Cc: users, dev
On Fri, 22 Jul 2016 14:19:29 -0700
Prabahar Radhakrishnan <prab@viptela.com> wrote:
> Hi,
> I was running a dpdk application with e1000 driver and I am facing a
> rare driver lockup condition. Under this condition, what I am seeing is
> that the Receive side locks up. The transmit side is fine. When I execute
> "rte_eth_dev_stop()/rte_eth_dev_start()" from within the VM, the dpdk
> application recovers. The lockup happens once in 2 or 3 days if I
> continuously ping an IP address serviced by the dpdk application. Once it
> locks up, what I am noticing is that even though packets are coming in, the
> driver is not populating them and signaling the event. In other words, in
> "eth_em_recv_pkts" call, I am not seeing "E1000_RXD_STAT_DD" being set for
> status, and the driver bails out. If anyone has come across such
> condition, please let me know? Appreciate the help.
>
> Environment: I have a VM running on top of Ubuntu/KVM.
> Application: Running dpdk-2.0.0.
> VM: uses e1000 driver.
> On the KVM side, our port is sitting in a bridge. There are other VNFs
> that we use for testing and some of them are using virtio driver.
>
> Thank You
> regards Prab
Save yourself lots of pain, use virtio not e1000 with DPDK.
The emulation of E1000 in QEMU is very limited and DPDK expects real hardware.
Lots of features and control are missing.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-07-22 22:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-07-22 21:19 [dpdk-dev] em1000 driver lockup in KVM Prabahar Radhakrishnan
2016-07-22 22:39 ` Stephen Hemminger
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).