From: Jerin Jacob <jerinjacobk@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dpdk-dev <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] config: increase default maximum number of NUMA nodes
Date: Thu, 4 Feb 2021 11:49:57 +0530 [thread overview]
Message-ID: <CALBAE1M1n591eRHBMsa0oXtGhameCcjJXqbcbUKpQ8GXPZTfpA@mail.gmail.com> (raw)
In-Reply-To: <20210203211818.3047146-1-thomas@monjalon.net>
On Thu, Feb 4, 2021 at 2:49 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> AMD CPU can present a high number of NUMA nodes.
> The default should be 32 for better compatibility.
The typical configuration is 4 nodes[1] for AMD. Just wondering, Is it
an exception case? if so, Do we need to consume more memory for normal
cases?
[1]
https://developer.amd.com/wp-content/resources/56308-NUMA%20Topology%20for%20AMD%20EPYC%E2%84%A2%20Naples%20Family%20Processors.PDF
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> meson_options.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meson_options.txt b/meson_options.txt
> index 5c382487da..6eff62e47d 100644
> --- a/meson_options.txt
> +++ b/meson_options.txt
> @@ -26,7 +26,7 @@ option('max_ethports', type: 'integer', value: 32,
> description: 'maximum number of Ethernet devices')
> option('max_lcores', type: 'integer', value: 128,
> description: 'maximum number of cores/threads supported by EAL')
> -option('max_numa_nodes', type: 'integer', value: 4,
> +option('max_numa_nodes', type: 'integer', value: 32,
> description: 'maximum number of NUMA nodes supported by EAL')
> option('enable_trace_fp', type: 'boolean', value: false,
> description: 'enable fast path trace points.')
> --
> 2.30.0
>
next prev parent reply other threads:[~2021-02-04 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 21:18 Thomas Monjalon
2021-02-04 6:19 ` Jerin Jacob [this message]
2021-02-04 10:28 ` Thomas Monjalon
2021-02-04 11:39 ` Jerin Jacob
2021-02-04 9:56 ` Bruce Richardson
2021-02-05 16:36 ` Thomas Monjalon
2021-02-04 10:56 ` Asaf Penso
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=CALBAE1M1n591eRHBMsa0oXtGhameCcjJXqbcbUKpQ8GXPZTfpA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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).