LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: davids@webmaster.com
Cc: "linux-kernel mailing list" <linux-kernel@vger.kernel.org>,
<jbarnes@engr.sgi.com>
Subject: Re: How can I optimize a process on a NUMA architecture(x86-64 specifically)?
Date: Sun, 23 May 2004 13:57:45 +0200 [thread overview]
Message-ID: <m3d64vtkxy.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1YRnC-3vk-5@gated-at.bofh.it> (David Schwartz's message of "Sun, 23 May 2004 05:00:12 +0200")
"David Schwartz" <davids@webmaster.com> writes:
> I don't think we've reached the point yet where treating x86-64 systems as
> NUMA machines makes very much sense.
Benchmarks disagree with you on that. In most cases local memory
policy seems to work better than BIOS interleaving. That's because
memory latency is usually more important than memory bandwidth.
-Andi
next prev parent reply other threads:[~2004-05-23 11:57 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
2004-05-25 1:09 ` Brett E.
[not found] ` <1YRnC-3vk-5@gated-at.bofh.it>
2004-05-23 11:57 ` Andi Kleen [this message]
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=m3d64vtkxy.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=davids@webmaster.com \
--cc=jbarnes@engr.sgi.com \
--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;
as well as URLs for NNTP newsgroup(s).