From mboxrd@z Thu Jan 1 00:00:00 1970 From: nickcooper-zhangtonghao Subject: Re: [PATCH v2 1/5] eal: Set numa node value for system which not support NUMA. Date: Mon, 9 Jan 2017 10:06:29 +0800 Message-ID: References: <1483617709-7088-1-git-send-email-nic@opencloud.tech> <8cb35df0-cdd6-143c-4f78-379a89f44616@intel.com> Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Ferruh Yigit , "dev@dpdk.org" To: Yong Wang Return-path: Received: from smtpbgbr2.qq.com (smtpbgbr2.qq.com [54.207.22.56]) by dpdk.org (Postfix) with ESMTP id 24ECE1E2B for ; Mon, 9 Jan 2017 03:06:26 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > On Jan 6, 2017, at 8:01 AM, Yong Wang 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