From: Stephen Hemminger <stephen@networkplumber.org>
To: Prabahar Radhakrishnan <prab@viptela.com>
Cc: users@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-dev] em1000 driver lockup in KVM
Date: Fri, 22 Jul 2016 15:39:32 -0700 [thread overview]
Message-ID: <20160722153932.15d08ef9@xeon-e3> (raw)
In-Reply-To: <CABgWcYrVuiEa0O5W0v4W1kzgQUNHCUugGb_f8TCy7NyNNAi6BA@mail.gmail.com>
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.
prev parent reply other threads:[~2016-07-22 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 21:19 Prabahar Radhakrishnan
2016-07-22 22:39 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160722153932.15d08ef9@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=prab@viptela.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).