From: Antonio Di Bacco <a.dibacco.ks@gmail.com>
To: "Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: AMD NPS bios change is is not reflected onto NUMA domains detected by DPDK 21.11
Date: Fri, 22 Apr 2022 17:51:54 +0200 [thread overview]
Message-ID: <CAO8pfFkGu17vkJZ3uGoLsJtDOh5Qvf9ccGdXBHTKJ_Tg-MdLNQ@mail.gmail.com> (raw)
In-Reply-To: <CY4PR12MB162343815985BF400285736386F79@CY4PR12MB1623.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
This was it !!!
Thanks.
Il giorno ven 22 apr 2022 alle ore 14:49 Tummala, Sivaprasad <
Sivaprasad.Tummala@amd.com> ha scritto:
> [AMD Official Use Only]
>
>
>
> Hi Antonio,
>
>
>
> You need to change the BIOS parameter “L3 Cache as NUMA Domain” to
> “Disable”.
>
> With this, each L3 cache will not be reported as a NUMA domain (/NUMA
> node).
>
>
>
> Thank you!
>
>
>
> *From:* Antonio Di Bacco <a.dibacco.ks@gmail.com>
> *Sent:* Friday, April 22, 2022 10:22 AM
> *To:* users@dpdk.org
> *Subject:* AMD NPS bios change is is not reflected onto NUMA domains
> detected by DPDK 21.11
>
>
>
> Using an AMD EPYC 7713 64-Core Processor (there are two on the server)
> for a total of 128 cores.
>
>
>
> If I change the NPS (numa per socket) in BIOS and power cycle the system
> and the I launch a DPDK application, I always get this message:
>
>
>
> EAL: Detected CPU lcores: 128
> EAL: Detected NUMA nodes: 16
>
>
>
> NPS is able to change the number of NUMA but DPDK always detects 16 NUMA
> domains.
>
> I tried with NPS1, NPS2, NPS4.
>
>
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3474 bytes --]
prev parent reply other threads:[~2022-04-22 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 9:22 Antonio Di Bacco
[not found] ` <DM6PR02MB5017C8B3DE4B5EC022AE3085D0F79@DM6PR02MB5017.namprd02.prod.outlook.com>
2022-04-22 12:49 ` Tummala, Sivaprasad
2022-04-22 15:51 ` Antonio Di Bacco [this message]
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=CAO8pfFkGu17vkJZ3uGoLsJtDOh5Qvf9ccGdXBHTKJ_Tg-MdLNQ@mail.gmail.com \
--to=a.dibacco.ks@gmail.com \
--cc=Sivaprasad.Tummala@amd.com \
--cc=users@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).