From: Christoph Lameter <cl@linux.com>
To: Andrew Dickinson <andrew@whydna.net>
Cc: linux-mm@kvack.org
Subject: Re: Memory/CPU affinity and Nehalem/QPI
Date: Tue, 28 Apr 2009 13:38:01 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0904281337100.13862@qirst.com> (raw)
In-Reply-To: <606676310904280915i3161fc90h367218482b19bbd6@mail.gmail.com>
On Tue, 28 Apr 2009, Andrew Dickinson wrote:
> I'm now testing a dual-package Nehalem system. If I understand this
> architecture correctly, each package's memory controller is driving
> its own bank of RAM. In my ideal world, I'd be able to provide a hint
> to kmalloc (or friends) such that my encode-table is stored close to
> one package and my decode-table is stored close to the other package.
> Is this something that I can control? If so, how? Does this matter
> with Intel's QPI or am I wasting my time?
You would need to configure your kernel with NUMA support. Then the
Nehalem system should boot with two NUMA nodes. The usual NUMA tools can
then be used to select memory allocation (see numactl() etc).
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-04-28 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 16:15 Andrew Dickinson
2009-04-28 16:52 ` Lee Schermerhorn
2009-04-28 17:38 ` Christoph Lameter [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=alpine.DEB.1.10.0904281337100.13862@qirst.com \
--to=cl@linux.com \
--cc=andrew@whydna.net \
--cc=linux-mm@kvack.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