From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chao Zhu Subject: Re: Fwd: [PATCH] PPC: Fix NUMA node numbering on IBM POWER8 LE machine Date: Thu, 17 Sep 2015 16:56:14 +0800 Message-ID: <55FA802E.8030808@linux.vnet.ibm.com> References: <1439554788-31037-1-git-send-email-chaozhu@linux.vnet.ibm.com> <55F7CCE9.8060807@linux.vnet.ibm.com> <20150915090122.GA27696@bricha3-MOBL3> <55F8CDC4.9040409@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" To: David Marchand Return-path: Received: from e28smtp07.in.ibm.com (e28smtp07.in.ibm.com [122.248.162.7]) by dpdk.org (Postfix) with ESMTP id 03C2E58D4 for ; Thu, 17 Sep 2015 10:57:48 +0200 (CEST) Received: from /spool/local by e28smtp07.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 17 Sep 2015 14:27:47 +0530 Received: from d28relay01.in.ibm.com (d28relay01.in.ibm.com [9.184.220.58]) by d28dlp03.in.ibm.com (Postfix) with ESMTP id 42E7D1258020 for ; Thu, 17 Sep 2015 14:27:11 +0530 (IST) Received: from d28av05.in.ibm.com (d28av05.in.ibm.com [9.184.220.67]) by d28relay01.in.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id t8H8vg6v64290820 for ; Thu, 17 Sep 2015 14:27:42 +0530 Received: from d28av05.in.ibm.com (localhost [127.0.0.1]) by d28av05.in.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id t8H8vfCw008605 for ; Thu, 17 Sep 2015 14:27:41 +0530 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" David, Let me take a look. On 2015/9/16 16:09, David Marchand wrote: > Hello Chao, > > On Wed, Sep 16, 2015 at 4:02 AM, Chao Zhu > wrote: > > Actually, without this change, DPDK can't work properly on PPC64 > little endian platform. It'll report "EAL: Not enough memory > available! Requested: xxxMB, available: xxxMB" such kind of error. > But for users, they don't know that changing the value of > CONFIG_RTE_MAX_NUMA_NODES can fix this. That why I invoke this patch. > > > Sorry, I forgot to reply in this thread. > > Well, to me, this is a workaround. > Yes it will work, but what happens if tomorrow we have some hardware > that tells us that it has some numa node which 60000 index ? > > I think we need a rework in eal to proerly handle this, like I said in > this mail : > http://dpdk.org/ml/archives/dev/2015-September/023630.html > > Do you think you can look into this ? > > > Thanks. > > -- > David Marchand