From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpbg65.qq.com (smtpbg65.qq.com [103.7.28.233]) by dpdk.org (Postfix) with ESMTP id 0A12A108F for ; Wed, 18 Jan 2017 03:41:55 +0100 (CET) X-QQ-mid: bizesmtp13t1484707307tggoocbd Received: from [10.0.117.171] (unknown [106.120.127.11]) by esmtp4.qq.com (ESMTP) with id ; Wed, 18 Jan 2017 10:41:45 +0800 (CST) X-QQ-SSF: 01100000002000F0F970B00A0000000 X-QQ-GoodBg: 0 From: nickcooper-zhangtonghao Message-Id: <72AA715B-7728-446E-BEE0-DA63EF0DFA60@opencloud.tech> Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\)) Date: Wed, 18 Jan 2017 10:41:48 +0800 In-Reply-To: Cc: "ferruh.yigit@intel.com" , "dev@dpdk.org" To: Yong Wang References: <1483930780-7064-1-git-send-email-nic@opencloud.tech> X-Mailer: Apple Mail (2.3226) X-QQ-SENDSIZE: 520 X-QQ-Bgrelay: 1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH v3 1/4] vmxnet3: Avoid memory leak in vmxnet3_dev_rx_queue_setup. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2017 02:41:57 -0000 > On Jan 18, 2017, at 10:05 AM, Yong Wang wrote: >=20 > Any downside with free/reallocation now that memzone can be freed? = Allocation with max ring size should work but is kind of wasteful in = terms of memory usage and I assume this type of ring size change should = not be a frequent operation. Not free/realloc them anymore. I guess it is necessary to use the allocation with max ring size. The seg fault really bother us. and the app (e.g. ovs) may change it frequently when tuning performance.=