From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>, brettspamacct@fastclick.com
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: How can I optimize a process on a NUMA architecture(x86-64 specifically)?
Date: Fri, 21 May 2004 12:08:16 -0700 [thread overview]
Message-ID: <86690000.1085166496@flay> (raw)
In-Reply-To: <200405211458.14304.jbarnes@engr.sgi.com>
>> Without these two things the kernel will
>> just allocate on the currently running CPU whatever that may be when in
>> fact a preference must be given to a CPU at some point, hopefully early
>> on in the life of the process, in order to take advantage of NUMA.
>
> The kernel does a pretty good job of keeping processes on the CPU they've been
> running on, and thus they'll probably stay close to their memory. But
> without explicit pinning, there's no guarantee.
One thing I *do* want to do, is instead of explicit homenodes, is to take
into account the per-node RSS of processes when doing my migration decisions.
That gives us a kind of dynamic homenode. I have the per-node RSS code in
my tree already from someone (Matt?), but we haven't used it. Of course,
this throws off the O(1)-ness of balancing decisions, but as long as we
cap the number we look at, and only do it for cross-node rebalance migrates
(we don't need it for exec), I really don't care ;-)
M.
next prev parent reply other threads:[~2004-05-21 19:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 0:51 How can I optimize a process on a NUMA architecture(x86-64 specifically)? 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 [this message]
2004-05-23 2:49 ` David Schwartz
[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 ` 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
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=86690000.1085166496@flay \
--to=mbligh@aracnet.com \
--cc=brettspamacct@fastclick.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