From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: traffic no longer readable... Date: Wed, 20 May 2015 17:33:20 +0200 Message-ID: <6852878.Uu60uYFa2E@xps13> References: <4184471.eVetuCRXHp@neuralfour> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Jeff Weeks Return-path: 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 ; Wed, 20 May 2015 17:34:06 +0200 (CEST) Received: by wichy4 with SMTP id hy4so64548509wic.1 for ; Wed, 20 May 2015 08:34:05 -0700 (PDT) In-Reply-To: <4184471.eVetuCRXHp@neuralfour> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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?