From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sergio.gonzalez.monroy@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 21BFB5A57
 for <dev@dpdk.org>; Wed, 15 Jul 2015 11:57:09 +0200 (CEST)
Received: from orsmga002.jf.intel.com ([10.7.209.21])
 by orsmga101.jf.intel.com with ESMTP; 15 Jul 2015 02:57:09 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.15,479,1432623600"; d="scan'208";a="764822256"
Received: from smonroyx-mobl.ger.corp.intel.com (HELO [10.237.221.48])
 ([10.237.221.48])
 by orsmga002.jf.intel.com with ESMTP; 15 Jul 2015 02:57:08 -0700
Message-ID: <55A62E73.8060503@intel.com>
Date: Wed, 15 Jul 2015 10:57:07 +0100
From: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: damu <2103458176@qq.com>
References: <tencent_06BE1BD20BEC88F81E937905@qq.com>
In-Reply-To: <tencent_06BE1BD20BEC88F81E937905@qq.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] App crash when using no-huge option
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <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: Wed, 15 Jul 2015 09:57:10 -0000

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 <cchemparathy@ezchip.com>
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