From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Gonzalez Monroy, Sergio" Subject: Re: App crash when using no-huge option Date: Wed, 15 Jul 2015 10:57:07 +0100 Message-ID: <55A62E73.8060503@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: dev To: damu <2103458176@qq.com> Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 21BFB5A57 for ; Wed, 15 Jul 2015 11:57:09 +0200 (CEST) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 15/07/2015 08:34, damu wrote: > Hi, > > Today I tried no-huge option with app/test, the test app crashed. > It seems that memory can not be allocated. > I think it could be this change causing the panic. Can someone check it? > > Hi Damu, Actually it is the following commit causing the panic: commit b3dfffd962ecd7a1d8700193b4b3305dc85e7ae4 Author: Cyril Chemparathy Date: Thu Jul 9 16:25:15 2015 +0800 mem: allow multiple page sizes to be requested Cause is that since allowing multiple page sizes it always expects the hugepage_sz field to be set to a value, but when using --no-huge, the field hugepage_sz is 0 and the logic does not work as expected. The issue could be fixed but adding logic to expect hugepage_sz being 0 or by setting hugepage_sz to a value (RTE_PGSIZE_4K) when using --no-huge. The latter would be my preference. I'll send a patch fixing it. Sergio