From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: traffic no longer readable...
Date: Wed, 20 May 2015 18:31:33 +0200
Message-ID: <1912621.IS2FFEymAS@xps13>
References: <1612889.HZQ1eI9Ptg@neuralfour>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org
To: Jeff Weeks <jweeks@neuraldk.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com
 [209.85.212.179]) by dpdk.org (Postfix) with ESMTP id 6F2B6568B
 for <dev@dpdk.org>; Wed, 20 May 2015 18:32:18 +0200 (CEST)
Received: by wizk4 with SMTP id k4so161586690wiz.1
 for <dev@dpdk.org>; Wed, 20 May 2015 09:32:18 -0700 (PDT)
In-Reply-To: <1612889.HZQ1eI9Ptg@neuralfour>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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@neuraldk.org>
> To: Thomas Monjalon <thomas.monjalon@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