From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 4D3618B27 for ; Sun, 12 Oct 2014 15:10:54 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id A263980C50B; Sun, 12 Oct 2014 06:17:38 -0700 (PDT) Date: Sun, 12 Oct 2014 06:17:38 -0700 From: Matthew Hall To: Yan Freedland Message-ID: <20141012131738.GB3672@mhcomputing.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] DPDK - VIRTIO performance problems 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: Sun, 12 Oct 2014 13:10:54 -0000 On Sun, Oct 12, 2014 at 12:37:37PM +0000, Yan Freedland wrote: > Every ~2min traffic stopped completely and then immediately came back. This > happened in a periodic fashion. To me it sounds like it could be similar to what I've seen when I ran out of mbuf's or ran out of RX / TX descriptor entries. It could be worth checking the error counters on the interfaces with DPDK and Linux OS / ethtool to see what might be incrementing during the failed time periods. Matthew.