From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ILCAS2.corp.radware.com (mailout1.radware.com [192.115.180.130]) by dpdk.org (Postfix) with ESMTP id B58F558E6 for ; Mon, 13 Oct 2014 08:57:00 +0200 (CEST) Received: from ILMB1.corp.radware.com ([fe80::78a5:d515:e805:d2a9]) by ILCAS2.corp.radware.com ([fe80::98f0:5e5c:9ac:6e36%10]) with mapi id 14.03.0195.001; Mon, 13 Oct 2014 10:04:38 +0300 From: Yan Freedland To: "Ouyang, Changchun" , Matthew Hall Thread-Topic: [dpdk-dev] DPDK - VIRTIO performance problems Thread-Index: Ac/mF9x0VsTVAtJFQYyNjYdyT+DFSv//28YAgADojID//41RIA== Date: Mon, 13 Oct 2014 07:04:38 +0000 Message-ID: References: <20141012131738.GB3672@mhcomputing.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [176.200.121.206] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: Mon, 13 Oct 2014 06:57:01 -0000 Hi I found that what blocked me was actually the "nf_conntrack", So enlarging the maximum there solved the issue. Thanks=20 Yan -----Original Message----- From: Ouyang, Changchun [mailto:changchun.ouyang@intel.com]=20 Sent: Monday, October 13, 2014 6:10 AM To: Matthew Hall; Yan Freedland Cc: dev@dpdk.org; Ouyang, Changchun Subject: RE: [dpdk-dev] DPDK - VIRTIO performance problems Hi , > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Matthew Hall > Sent: Sunday, October 12, 2014 9:18 PM > To: Yan Freedland > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] DPDK - VIRTIO performance problems >=20 > 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. >=20 > To me it sounds like it could be similar to what I've seen when I ran=20 > out of mbuf's or ran out of RX / TX descriptor entries. It could be=20 > worth checking the error counters on the interfaces with DPDK and=20 > Linux OS / ethtool to see what might be incrementing during the failed ti= me periods. >=20 I didn't meet this issue before, I am not sure if the following patch will fix this issue or not. Please try= it. http://dpdk.org/dev/patchwork/patch/779/ By the way, what kind of backend did you use? User space vhost, or other backend? Thanks Changchun