From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Andrew Theurer <habanero@us.ibm.com>
Cc: Andi Kleen <ak@muc.de>, "Bryan O'Sullivan" <bos@serpentine.com>,
brettspamacct@fastclick.com,
"Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel@vger.kernel.org
Subject: Re: How can I optimize a process on a NUMA architecture(x86-64 specifically)?
Date: Mon, 24 May 2004 20:27:09 -0400 [thread overview]
Message-ID: <40B292DD.5060500@coyotegulch.com> (raw)
In-Reply-To: <200405241700.57249.habanero@us.ibm.com>
Andrew Theurer wrote:
> FYI Brett, some Opteron systems have a BIOS option to interleave memory. If
> you are going to make use of NUMA, I think you want to not interleave.
I can confirm this. On my Tyan Thunder K8W 2885 (dual Opteron), I had to
disable interleaving (under the Northbridge setup) before Linux
recognized it as a NUMA system.
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Software Invention for High-Performance Computing
next prev parent reply other threads:[~2004-05-25 0:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1Y6yr-eM-11@gated-at.bofh.it>
[not found] ` <1YbRm-4iF-11@gated-at.bofh.it>
[not found] ` <1Yma3-4cF-3@gated-at.bofh.it>
[not found] ` <1YmjP-4jX-37@gated-at.bofh.it>
2004-05-21 19:17 ` How can I optimize a process on a NUMA architecture(x86-64 specifically)? Andi Kleen
[not found] ` <1YmMN-4Kh-17@gated-at.bofh.it>
[not found] ` <1Yn67-50q-7@gated-at.bofh.it>
2004-05-21 19:19 ` Andi Kleen
2004-05-21 20:32 ` Martin J. Bligh
2004-05-21 23:42 ` Brett E.
2004-05-22 6:13 ` Martin J. Bligh
2004-05-22 7:41 ` Andi Kleen
2004-05-23 0:28 ` Bryan O'Sullivan
2004-05-23 14:28 ` Andi Kleen
2004-05-24 22:00 ` Andrew Theurer
2004-05-25 0:27 ` Scott Robert Ladd [this message]
2004-05-25 1:09 ` Brett E.
[not found] ` <1YRnC-3vk-5@gated-at.bofh.it>
2004-05-23 11:57 ` Andi Kleen
2004-05-21 0:51 Brett E.
2004-05-21 1:29 ` Jesse Barnes
2004-05-21 6:37 ` Martin J. Bligh
2004-05-21 17:27 ` Brett E.
2004-05-21 17:46 ` Martin J. Bligh
2004-05-21 18:14 ` Brett E.
2004-05-21 18:30 ` Martin J. Bligh
2004-05-21 18:58 ` Jesse Barnes
2004-05-21 19:08 ` Martin J. Bligh
2004-05-23 2:49 ` David Schwartz
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=40B292DD.5060500@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=ak@muc.de \
--cc=bos@serpentine.com \
--cc=brettspamacct@fastclick.com \
--cc=habanero@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.