From: Chao Zhu <chaozhu@linux.vnet.ibm.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Fwd: [PATCH] PPC: Fix NUMA node numbering on IBM POWER8 LE machine
Date: Wed, 16 Sep 2015 10:02:44 +0800 [thread overview]
Message-ID: <55F8CDC4.9040409@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150915090122.GA27696@bricha3-MOBL3>
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.
On 2015/9/15 17:01, Bruce Richardson wrote:
> On Tue, Sep 15, 2015 at 03:46:49PM +0800, Chao Zhu wrote:
>> Any response of this patch?
> Looks ok to me - pretty trivial change.
>
> /Bruce
>> -------- Forwarded Message --------
>> Subject: [dpdk-dev] [PATCH] PPC: Fix NUMA node numbering on IBM POWER8 LE
>> machine
>> Date: Fri, 14 Aug 2015 20:19:48 +0800
>> From: Chao Zhu <chaozhu@linux.vnet.ibm.com>
>> To: dev@dpdk.org
>>
>>
>>
>> When Linux is running on bare metal, it gets the raw hardware
>> information. On POWER8 little endian bare metal machine, the node number
>> is not continuous. It will jump from 0 to other values, for example, it
>> can be 0, 1, 16, 17. This patch modified the CONFIG_RTE_MAX_NUMA_NODES
>> value to make dpdk work on POWER8 bare metal little endian machine.
>>
>> Signed-off-by: Chao Zhu <chaozhu@linux.vnet.ibm.com>
>> ---
>> config/common_linuxapp | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/config/common_linuxapp b/config/common_linuxapp
>> index 0de43d5..82a027e 100644
>> --- a/config/common_linuxapp
>> +++ b/config/common_linuxapp
>> @@ -98,7 +98,7 @@ CONFIG_RTE_NEXT_ABI=y
>> #
>> CONFIG_RTE_LIBRTE_EAL=y
>> CONFIG_RTE_MAX_LCORE=128
>> -CONFIG_RTE_MAX_NUMA_NODES=8
>> +CONFIG_RTE_MAX_NUMA_NODES=32
>> CONFIG_RTE_MAX_MEMSEG=256
>> CONFIG_RTE_MAX_MEMZONE=2560
>> CONFIG_RTE_MAX_TAILQ=32
>> --
>> 1.7.1
>>
>>
>>
next prev parent reply other threads:[~2015-09-16 2:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 12:19 [dpdk-dev] " Chao Zhu
2015-09-15 7:46 ` [dpdk-dev] Fwd: " Chao Zhu
2015-09-15 9:01 ` Bruce Richardson
2015-09-16 2:02 ` Chao Zhu [this message]
2015-09-16 8:09 ` David Marchand
2015-09-17 8:56 ` Chao Zhu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55F8CDC4.9040409@linux.vnet.ibm.com \
--to=chaozhu@linux.vnet.ibm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).