From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Marchand Subject: Re: Fwd: [PATCH] PPC: Fix NUMA node numbering on IBM POWER8 LE machine Date: Wed, 16 Sep 2015 10:09:16 +0200 Message-ID: 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 Cc: "dev@dpdk.org" To: Chao Zhu Return-path: Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) by dpdk.org (Postfix) with ESMTP id 65D093239 for ; Wed, 16 Sep 2015 10:09:17 +0200 (CEST) Received: by oibi136 with SMTP id i136so116556787oib.3 for ; Wed, 16 Sep 2015 01:09:16 -0700 (PDT) In-Reply-To: <55F8CDC4.9040409@linux.vnet.ibm.com> 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" 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