From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ; Wed, 20 May 2015 18:32:18 +0200 (CEST) Received: by wizk4 with SMTP id k4so161586690wiz.1 for ; Wed, 20 May 2015 09:32:18 -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=lCX333gcOy/gKqRhFbDpVngnBNdy+v/o+bxlYIbMp8g=; b=ZFUt774i0KmNwWL4mpdms4IPevIPifrK97mdKuqcEZ+XpyJTA0qObAkbSfHXYiNGoh WdOoYORYS+kfg4Pj9dGdUCx7/bqoeN4NvVIlrac29ygts5phfe+Vh45uUBWR1wZYCnBe 9aD0e2EDdzENrOvxfLnvkdQ9ESwcvCrluW+5emblykKfbW/BIBLIB5APS2yklVa6wF4Y yYL+4aGBOzVwV/JkRm4xN+OETYypU6MJh1EG70auhOJS1jxDJFKqTnz9MoQl3K967EXQ iDaTBiInj0V3WYzLC4a6OeEgRz6RW93EIs/YztieoRDBKtQnrBqyX009zjyh/LdHIyyP J/7w== X-Gm-Message-State: ALoCoQme8b5N2gpVatz+OopJDpq+qDDOT9jp0Xv6l4dS1JLiaOBO2Ic6XtRs2yECamMR8VSjPAb6 X-Received: by 10.180.82.100 with SMTP id h4mr26538102wiy.61.1432139538307; Wed, 20 May 2015 09:32:18 -0700 (PDT) Received: from xps13.localnet ([62.159.77.186]) by mx.google.com with ESMTPSA id h5sm27651446wjn.20.2015.05.20.09.32.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 May 2015 09:32:17 -0700 (PDT) From: Thomas Monjalon To: Jeff Weeks Date: Wed, 20 May 2015 18:31:33 +0200 Message-ID: <1912621.IS2FFEymAS@xps13> Organization: 6WIND User-Agent: KMail/4.14.7 (Linux/4.0.1-1-ARCH; KDE/4.14.7; x86_64; ; ) In-Reply-To: <1612889.HZQ1eI9Ptg@neuralfour> References: <1612889.HZQ1eI9Ptg@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2015 16:32:18 -0000 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 > To: Thomas Monjalon > > 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