From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com
 [209.85.212.175]) by dpdk.org (Postfix) with ESMTP id 09C465698
 for <dev@dpdk.org>; Wed, 20 May 2015 17:34:06 +0200 (CEST)
Received: by wichy4 with SMTP id hy4so64548509wic.1
 for <dev@dpdk.org>; Wed, 20 May 2015 08:34:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=K5Ku+JVzkld1gxiV/+DxUaG/20ubVjerKNfCmesKgnU=;
 b=ZJCPcgMRLKoG9DfgPf9aII+QgJwm1URMjHZxmB6F4TNd4TfZolcIkUObtfXDCHwpcc
 JCB8pRIPuK63uOzZv7v6Mv5B4rvny9ryFFh7ZUdL3CvxEehbRlLXuDZNclPiTBJA687T
 E7auyPjmHGC5u0oPIeuPWbiAaCGzcwBTVsU1fadXWhxzAcyBHLnAy9gQXH3g0XhxGMYz
 FZn+SFv+qq8LI3CYXBioA0mcixOG9YPNMmen3J39bH0v20zjgMEJVsXMGduaS0WCy9YI
 Dz6/zZtTiwv/fZKEuUQicepT0k6ei9R64L0p7VorSAwfKlQ9DcjKRzQZZLHhcbhK+sjr
 KfLQ==
X-Gm-Message-State: ALoCoQmJPBoJVeBVZpJW6j1oHhwqLz/nWE4iFAw5SrQUk41YJLz4OyHMhOF4Gd+TUS0uYtJBG2k5
X-Received: by 10.194.78.12 with SMTP id x12mr63480608wjw.112.1432136045624;
 Wed, 20 May 2015 08:34:05 -0700 (PDT)
Received: from xps13.localnet ([62.159.77.186])
 by mx.google.com with ESMTPSA id js3sm27403884wjc.5.2015.05.20.08.34.04
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Wed, 20 May 2015 08:34:04 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jeff Weeks <jweeks@neuraldk.org>
Date: Wed, 20 May 2015 17:33:20 +0200
Message-ID: <6852878.Uu60uYFa2E@xps13>
Organization: 6WIND
User-Agent: KMail/4.14.7 (Linux/4.0.1-1-ARCH; KDE/4.14.7; x86_64; ; )
In-Reply-To: <4184471.eVetuCRXHp@neuralfour>
References: <4184471.eVetuCRXHp@neuralfour>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] traffic no longer readable...
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
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>
X-List-Received-Date: Wed, 20 May 2015 15:34:06 -0000

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?