From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.execulink.net (smtp2.execulink.net [69.63.44.83]) by dpdk.org (Postfix) with ESMTP id 2550AC324 for ; Wed, 20 May 2015 17:10:28 +0200 (CEST) Received: from 188-118.speede.golden.net ([216.75.188.118] helo=neuralfour.localnet) by smtp2.execulink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1Yv5da-0000fY-S3 for dev@dpdk.org; Wed, 20 May 2015 11:10:27 -0400 From: Jeff Weeks To: dev@dpdk.org Date: Wed, 20 May 2015 11:11:50 -0400 Message-ID: <4184471.eVetuCRXHp@neuralfour> User-Agent: KMail/4.14.6 (Linux/3.16.7-21-desktop; KDE/4.14.6; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2015 15:10:28 -0000 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? Thanks, Jeff