From: Chao Zhu <chaozhu@linux.vnet.ibm.com>
To: dev@dpdk.org, thomas.monjalon@6wind.com
Subject: [dpdk-dev] Fwd: [PATCH] PPC: Fix NUMA node numbering on IBM POWER8 LE machine
Date: Tue, 15 Sep 2015 15:46:49 +0800 [thread overview]
Message-ID: <55F7CCE9.8060807@linux.vnet.ibm.com> (raw)
In-Reply-To: <1439554788-31037-1-git-send-email-chaozhu@linux.vnet.ibm.com>
Any response of this patch?
-------- 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-15 7:47 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 ` Chao Zhu [this message]
2015-09-15 9:01 ` [dpdk-dev] Fwd: " Bruce Richardson
2015-09-16 2:02 ` Chao Zhu
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=55F7CCE9.8060807@linux.vnet.ibm.com \
--to=chaozhu@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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).