From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: Sivaprasad Tummala <sivaprasad.tummala@amd.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"konstantin.v.ananyev@yandex.ru" <konstantin.v.ananyev@yandex.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] config/x86: config support for AMD EPYC processors
Date: Tue, 7 Nov 2023 12:59:44 +0000 [thread overview]
Message-ID: <7a7a1fc0a6aa445090eff7d509918ab8@huawei.com> (raw)
In-Reply-To: <20230925151027.558546-1-sivaprasad.tummala@amd.com>
> -----Original Message-----
> From: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
> Sent: Monday, September 25, 2023 4:10 PM
> To: bruce.richardson@intel.com; konstantin.v.ananyev@yandex.ru
> Cc: dev@dpdk.org; Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
> Subject: [PATCH] config/x86: config support for AMD EPYC processors
>
> From: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
>
> By default, max lcores are limited to 128 for x86 platforms.
> On AMD EPYC processors, this limit needs to be increased to
> leverage all the cores.
>
> The patch adjusts the limit specifically for native compilation
> on AMD EPYC CPUs.
>
> Signed-off-by: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
> ---
> config/x86/meson.build | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/config/x86/meson.build b/config/x86/meson.build
> index d8ef50fb40..5355731cef 100644
> --- a/config/x86/meson.build
> +++ b/config/x86/meson.build
> @@ -83,4 +83,21 @@ endif
>
> dpdk_conf.set('RTE_CACHE_LINE_SIZE', 64)
> dpdk_conf.set('RTE_MAX_LCORE', 128)
> +
> +epyc_zen_cores = {
> + '__znver4__':512,
> + '__znver3__':256,
> + '__znver2__':256,
> + '__znver1__':128
> + }
> +
> +if get_option('platform') == 'native'
> + foreach m:epyc_zen_cores.keys()
> + if cc.get_define(m, args: machine_args) != ''
> + dpdk_conf.set('RTE_MAX_LCORE', epyc_zen_cores[m])
> + break
> + endif
> + endforeach
> +endif
> +
> dpdk_conf.set('RTE_MAX_NUMA_NODES', 32)
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>
> 2.34.1
next prev parent reply other threads:[~2023-11-07 12:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 15:10 Sivaprasad Tummala
2023-10-06 7:50 ` David Marchand
2023-10-16 5:14 ` Tummala, Sivaprasad
2023-10-16 5:20 ` Tummala, Sivaprasad
2023-10-17 9:45 ` Kevin Traynor
2023-10-17 10:27 ` Morten Brørup
2023-11-06 21:05 ` Thomas Monjalon
2023-11-06 22:17 ` Morten Brørup
2023-11-07 13:13 ` Konstantin Ananyev
2023-11-07 13:30 ` Morten Brørup
2023-11-07 14:32 ` Konstantin Ananyev
2023-11-08 12:24 ` Tummala, Sivaprasad
2023-11-08 13:06 ` Morten Brørup
2023-11-09 16:43 ` Konstantin Ananyev
2023-10-17 10:58 ` Ferruh Yigit
2023-11-07 12:59 ` Konstantin Ananyev [this message]
2023-11-12 13:48 ` Thomas Monjalon
2023-12-20 7:10 Sivaprasad Tummala
2023-12-20 7:27 ` Morten Brørup
2023-12-20 9:22 ` Tummala, Sivaprasad
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=7a7a1fc0a6aa445090eff7d509918ab8@huawei.com \
--to=konstantin.ananyev@huawei.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=sivaprasad.tummala@amd.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).