2015-05-20 11:59, Jeff Weeks:
> forgot to include the list...
>
> ---------- Forwarded Message ----------
>
> Subject: Re: [dpdk-dev] traffic no longer readable...
> Date: Wednesday, May 20, 2015, 11:56:47 AM
> From: Jeff Weeks <jweeks at neuraldk.org>
> To: Thomas Monjalon <thomas.monjalon at 6wind.com>
>
> On Wednesday, May 20, 2015 05:33:20 PM you wrote:
> > 2015-05-20 11:11, Jeff Weeks:
> > > Hello all,
> > >
> > > I've been developing with dpdk, using virtio, and I'm noticing that I can
> > > often get into a state whereby I no longer receive any packets.
> > >
> > > The call to rte_eth_rx_burst always returns 0, indicating the rx queue is
> > > empty.
> > >
> > > How is this queue filled? I see there is a dpdk thread, which waits on an
> > > epoll fd for interrupts. I set a breakpoint here, and it appeared as
> > > though we were waiting forever on the epoll fd. This, to me, seemed to
> > > be the source of the issue I'm seeing (presumably interrupts cause us to
> > > read off the nic and fill the queue?)... but, oddly enough, I see the
> > > same behaviour even when I'm receiving packets.
> > >
> > > Have I misinterpreted how this is supposed to work? Or is gdb behaving
> > > poorly for me (wouldn't be surprising...).
> > >
> > > What/how else can I further investigate this?
> >
> > Are you using the latest version (git HEAD)?
> > Are you using DPDK vhost?
>
> I am using vhost, yes.
> I'm currently using 1.8. Is this a known issue fixed in HEAD, or 2.0?
Maybe it is due to this (fixed) bug:
http://dpdk.org/browse/dpdk/commit/?id=159793ac867
