From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Andi Kleen <ak@suse.de>,
akpm@osdl.org, Christoph Hellwig <hch@infradead.org>,
linux-ia64@vger.kernel.org, steiner@sgi.com,
linux-kernel@vger.kernel.org, Wu Fengguang <wfg@mail.ustc.edu.cn>,
discuss@x86-64.org
Subject: Re: [PATCH 1/3] Zone reclaim V3: main patch
Date: Thu, 8 Dec 2005 23:51:02 +0100 [thread overview]
Message-ID: <20051208225102.GW11190@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0512081320200.30786@schroedinger.engr.sgi.com>
> For Altix 20 means that the other node is remote but in the same
> enclosure / motherboard. Latency is very low in these cases. I think in
> these small configurations it is better to go off node rather than using
> the reclaim logic.
On Opterons the NUMA factors are usually < 2, more towards 1, but people
definitely note a difference between node and off node.
So I don't think that's a good heuristic.
I would use > LOCAL_DISTANCE or perhaps if you really want
a new constant with value 12-15.
> RECLAIM_DISTANCE can be set per arch if the default is not okay.
Well if anything it would be per system - perhaps need to make
it a boot option or somesuch later.
-Andi
next prev parent reply other threads:[~2005-12-08 22:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 20:37 [PATCH 1/3] Zone reclaim V3: main patch Christoph Lameter
2005-12-08 20:37 ` [PATCH 2/3] Zone reclaim V3: Remove debris from old zone reclaim Christoph Lameter
2005-12-08 20:37 ` [PATCH 3/3] Zone reclaim V3: Frequency of failed reclaim attempts Christoph Lameter
2005-12-08 20:52 ` Andi Kleen
2005-12-08 21:08 ` Christoph Lameter
2005-12-08 21:08 ` Christoph Lameter
2005-12-08 21:10 ` Andi Kleen
2005-12-08 21:08 ` [PATCH 1/3] Zone reclaim V3: main patch Andi Kleen
2005-12-08 21:23 ` Christoph Lameter
2005-12-08 22:51 ` Andi Kleen [this message]
2005-12-08 23:19 ` Christoph Lameter
2005-12-08 23:28 ` [discuss] " Andi Kleen
2005-12-08 23:35 ` Christoph Lameter
2005-12-08 23:40 ` Andi Kleen
2005-12-09 0:10 ` Christoph Lameter
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=20051208225102.GW11190@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=discuss@x86-64.org \
--cc=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=wfg@mail.ustc.edu.cn \
/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