From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <nic@opencloud.tech>
Received: from smtpbgbr2.qq.com (smtpbgbr2.qq.com [54.207.22.56])
 by dpdk.org (Postfix) with ESMTP id 24ECE1E2B
 for <dev@dpdk.org>; Mon,  9 Jan 2017 03:06:26 +0100 (CET)
X-QQ-mid: bizesmtp14t1483927581t2ye71if
Received: from [10.0.112.23] (unknown [106.120.127.11])
 by esmtp4.qq.com (ESMTP) with 
 id ; Mon, 09 Jan 2017 10:06:19 +0800 (CST)
X-QQ-SSF: 0110000000200070F770000A0000000
X-QQ-FEAT: eDvc/U510s0TlaUUvFc98z82CfquLP/eYPlG1bJpkHh3OM2DrVMqHW7F0KiJc
 LwcWmRQs0bLd59yIho4WvY9TO4UmxiVBNUvuJ62mkQsNR/j6ZKvUloTE/R0i1a972jOdCY2
 ajgKcLsINu2uFZTiiu/SzBu3uSjOYqSJLcYsD7NUK8T/gv9gkP3JuMTTsAy0nQplN40Cj7e
 SzNfIxCAt1pKUszEERmds4VvkLoyQYoG06+XHMXxuJMlj20noWUSfuTZhvu0EB4EM3uBVC7
 3utv04DaAQZqEpzBHS73bKWoc=
X-QQ-GoodBg: 0
From: nickcooper-zhangtonghao <nic@opencloud.tech>
Message-Id: <D457C98D-01E7-43B2-A402-8F914819728E@opencloud.tech>
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
Date: Mon, 9 Jan 2017 10:06:29 +0800
In-Reply-To: <BY2PR05MB2359F2C3447498DCFB38225BAF630@BY2PR05MB2359.namprd05.prod.outlook.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
 "dev@dpdk.org" <dev@dpdk.org>
To: Yong Wang <yongwang@vmware.com>
References: <1483617709-7088-1-git-send-email-nic@opencloud.tech>
 <8cb35df0-cdd6-143c-4f78-379a89f44616@intel.com>
 <BY2PR05MB2359F2C3447498DCFB38225BAF630@BY2PR05MB2359.namprd05.prod.outlook.com>
X-Mailer: Apple Mail (2.3226)
X-QQ-SENDSIZE: 520
X-QQ-Bgrelay: 1
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [dpdk-dev] [PATCH v2 1/5] eal: Set numa node value for system
 which not support NUMA.
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jan 2017 02:06:29 -0000


> On Jan 6, 2017, at 8:01 AM, Yong Wang <yongwang@vmware.com> wrote:
>=20
> Can you add the exact steps to reproduce the vmxnet3 issues to help =
the review and the verification. My guess is that you have stopped the =
device, changed some ring parameters (to something larger than the =
previous settings) and restarted the device.


Thanks for your reply. Your guess is right. I run the openvswitch+dpdk =
with vmxnet3.=20
First=EF=BC=8CI set the nb_desc of rx queue to 2048, and then stop the =
device=EF=BC=8C change nb_desc to 4096.
When I start the device again, I get the openvswitch crash caused by =
dpdk. Writing a sample program based on dpdk, I also get a crash.
The e1000 dpdk driver allocates RX ring for max possible mumber of =
hardware descriptors. I guess vmxnet3 should be in the same case.
I will submit v3.

Thanks.=20