From: Sheo Shanker Prasad <ssp@creativeresearch.org>
To: linux-kernel@vger.kernel.org
Subject: Please help with following NUMA-related questions
Date: Mon, 25 Jul 2005 06:47:31 -0700 [thread overview]
Message-ID: <200507250647.31803.ssp@creativeresearch.org> (raw)
I will greatly appreciate any help regarding the following matters:
(1) How to know whether my machine is NUMA-aware or not,
(2) Difference between memory bank interleaving and node interleaving
(3) When the BIOS asks me to set bank interleaving as AUTO, then it says that
AUTO allows memory access to spread out over banks on the same node or across
nodes decreasing memory access contentions. However, I have no idea when the
memory access is spread over banks on the same node or across nodes. I also
do not know how to tell the machine to access memory across the nodes or on
the same node. I have no idea as to how the AUTO choice affects
NUMA-awareness.
(4) The BIOS also tells me that I could choose bani interleaving as DISABLED.
But I do not know what its implications are for NUMA awareness.
Here are other relevant details. I have a dual-Opteron 250 (2.4GHz) set in
Tyan Thunder 2885 K8W with AMIBIOS version 2.05.
When I bought it last year, the machine was running under SuSE 9.1 Pro and the
Linux kernel was 2.6.5-7.108-smp. At that time both the Hardware Info from
YAST and /vat/log/messages were explicitly mentioning things :
Scanning NUMA topology in Northbridge 24
<6>Number of nodes 2 (10010)
<6>Node 0 MemBase 0000000000000000 Limit 000000007fffffff
<6>Node 1 MemBase 0000000080000000 Limit 00000000cbff0000
<6>Using node hash shift of 24
These messages indicated that NODE interleaving was off and the machine was
NUMA-aware.
Then, after a few months, the motherboard failed and the machine was sent to
the vendor for repair. It came back with SuSE 9.3 and the Linux kernel
version 2.6.11.4-21.7-smp (geeko@buildhost) (gcc version 3.3.5 20050117
(prerelease) (SUSE Linux)) #1 SMP Thu Jun 2 14:23:14 UTC 2005.
Now both the Hardware Info from YAST and /vat/log/messages DO NOT mention
NUMA anywhere, and I do not have anyway to check whether the
NODE-Interleaving is OFF or ON. My difficulties are compounded because I do
not know how to interpret the chipset related setting in the BIOS.
Currently, in the BIOS setting (Chipset->memory config -> Bank Interleaving),
I am asked to choose between AUTO & DISABLED. No choice is offered for Node
Interleaving.
The only guidance for the choice is that interleaving allows memory access to
spread out over banks on the same node or across nodes decreasing memory
access contentions. Nothing is mentioned about what happens when Interleaving
is disabled. Furthermore, if I choose AUTO, then I do not know when the
memory is spread out over banks on the same node or across nodes.
Any help will be greatly appreciated.
Thanking you in advance.
--
Best regards.
Sheo
(Sheo S. Prasad)
Creative Research Enterprises
6354 Camino del Lago
Pleasanton, CA 94566, USA
Voice Phone: (+1) 925 426-9341
Fax Phone: (+1) 925 426-9417
e-mail: ssp@CreativeResearch.org
next reply other threads:[~2005-07-25 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 13:47 Sheo Shanker Prasad [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-10 2:14 Please help with following NUMA-related questions Xie, Bill
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=200507250647.31803.ssp@creativeresearch.org \
--to=ssp@creativeresearch.org \
--cc=linux-kernel@vger.kernel.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