From: David Wilder <dwilder@us.ibm.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, bruce.richardson@intel.com,
pradeep@us.ibm.com, drc@ibm.com
Subject: [dpdk-dev] [PATCH] config: update RTE_MAX_LCORE for ppc build
Date: Wed, 5 Jun 2019 15:57:45 -0700 [thread overview]
Message-ID: <20190605225745.17100-1-dwilder@us.ibm.com> (raw)
Setting RTE_MAX_LCORE to reflect the largest available configuration.
Signed-off-by: David Wilder <dwilder@us.ibm.com>
---
I am splitting my previous patch "meson: Update flags and values for ppc_64"
into two separate patches (not a series). This is the second patch.
Updating values for both the meson and make builds per Thomas's comments.
config/defconfig_ppc_64-power8-linuxapp-gcc | 2 +-
config/ppc_64/meson.build | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/config/defconfig_ppc_64-power8-linuxapp-gcc b/config/defconfig_ppc_64-power8-linuxapp-gcc
index 7e248b7..04b04ce 100644
--- a/config/defconfig_ppc_64-power8-linuxapp-gcc
+++ b/config/defconfig_ppc_64-power8-linuxapp-gcc
@@ -36,7 +36,7 @@ CONFIG_RTE_ARCH="ppc_64"
CONFIG_RTE_ARCH_PPC_64=y
CONFIG_RTE_ARCH_64=y
-CONFIG_RTE_MAX_LCORE=256
+CONFIG_RTE_MAX_LCORE=1536
CONFIG_RTE_MAX_NUMA_NODES=32
CONFIG_RTE_CACHE_LINE_SIZE=128
diff --git a/config/ppc_64/meson.build b/config/ppc_64/meson.build
index 8c64445..0e65f9d 100644
--- a/config/ppc_64/meson.build
+++ b/config/ppc_64/meson.build
@@ -8,7 +8,7 @@ dpdk_conf.set('RTE_ARCH', 'ppc_64')
dpdk_conf.set('RTE_ARCH_PPC_64', 1)
# overrides specific to ppc64
-dpdk_conf.set('RTE_MAX_LCORE', 256)
+dpdk_conf.set('RTE_MAX_LCORE', 1536)
dpdk_conf.set('RTE_MAX_NUMA_NODES', 32)
dpdk_conf.set('RTE_CACHE_LINE_SIZE', 128)
dpdk_conf.set('RTE_MACHINE_CPUFLAG_ALTIVEC', 1)
--
1.8.3.1
next reply other threads:[~2019-06-05 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 22:57 David Wilder [this message]
2019-06-05 23:21 ` David Christensen
2019-07-04 15:56 ` Thomas Monjalon
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=20190605225745.17100-1-dwilder@us.ibm.com \
--to=dwilder@us.ibm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=drc@ibm.com \
--cc=pradeep@us.ibm.com \
--cc=thomas@monjalon.net \
/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).