From: Jaganathan Palanisamy <jpalanis@redhat.com>
To: users@dpdk.org
Subject: [dpdk-users] How to get the number of memory channels?
Date: Mon, 11 Dec 2017 17:39:21 +0530 [thread overview]
Message-ID: <CAJk1oW7dj7oW+VtKUq6-4phb67cgDpAFgU5kteOJe0Vp3o0kmA@mail.gmail.com> (raw)
We see that the output format of dmidecode is not consistent across
baremetals. Executed command "sudo dmidecode | grep 'DIMM' " on two
different machines and got different output formats.
Machine1 Output:
Locator: A1
Bank Locator: Not Specified
Locator: A2
Bank Locator: Not Specified
Locator: A3
Bank Locator: Not Specified
Locator: B1
Bank Locator: Not Specified
Locator: B2
Bank Locator: Not Specified
Locator: B3
Bank Locator: Not Specified
Machine2 Output:
Locator: PROC 1 DIMM 1
Bank Locator: Not Specified
Locator: PROC 1 DIMM 2
Bank Locator: Not Specified
Locator: PROC 1 DIMM 3
Bank Locator: Not Specified
Locator: PROC 2 DIMM 1
Bank Locator: Not Specified
Locator: PROC 2 DIMM 2
Bank Locator: Not Specified
Locator: PROC 2 DIMM 3
Bank Locator: Not Specified
Please let me know there is any other tools to identify the number of
memory channels per socket or we have to just rely on the hardware
manuals?
Thanks,
Jaganathan.
reply other threads:[~2017-12-11 12:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJk1oW7dj7oW+VtKUq6-4phb67cgDpAFgU5kteOJe0Vp3o0kmA@mail.gmail.com \
--to=jpalanis@redhat.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).