From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Christoph Lameter <cl@linux.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Chris McDermott <lcm@linux.vnet.ibm.com>
Subject: Re: [PATCH resend^2] mm: increase RECLAIM_DISTANCE to 30
Date: Tue, 24 May 2011 13:24:23 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1105241311260.14396@chino.kir.corp.google.com> (raw)
In-Reply-To: <20110524130700.079b09e8.akpm@linux-foundation.org>
On Tue, 24 May 2011, Andrew Morton wrote:
> How's that digging coming along?
>
> I'm pretty wobbly about this patch. Perhaps we should set
> RECLAIM_DISTANCE to pi/2 or something, to force people to correctly set
> the dang thing in initscripts.
>
I think RECLAIM_DISTANCE as a constant is the wrong approach to begin
with.
The distance between nodes as specified by the SLIT imply that a node with
a distance of 30 has a relative distance of 3x than a local memory access.
That's not the same as implying the latency is 3x greater, though, since
the SLIT is based on relative distances according to ACPI 3.0. In other
words, it's perfectly legitimate for node 0 to have a distance of 20 and
30 to nodes 1 and 2, respectively, if their memory access latencies are 5x
and 10x greater, while the SLIT would remain unchanged if the latencies
were 2x and 3x.
So basing zone reclaim by default off of a relative distance specified in
the SLIT is wrong to begin with, and that's probably why we notice that
the old value of 20 doesn't suffice on some machines anymore.
As I suggested earlier, I think it would be far better to actually measure
the memory access latency to remote nodes at boot to determine whether to
prefer zone reclaim or not rather than basing it off a false SLIT
assumption.
Notice also that the machines that this patch was proposed for probably
also didn't have a custom SLIT to begin with and so remote nodes get a
default value of REMOTE_DISTANCE, which equaled RECLAIM_DISTANCE. The
same effect would have been achieved if you had decreased REMOTE_DISTANCE
to 15.
We probably shouldn't be using SLIT distances at all within the kernel.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-05-24 20:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 8:19 KOSAKI Motohiro
2011-04-11 21:19 ` Andrew Morton
2011-04-12 0:59 ` KOSAKI Motohiro
2011-04-11 21:29 ` Dave Hansen
2011-04-12 1:01 ` KOSAKI Motohiro
2011-04-12 2:27 ` Dave Hansen
2011-04-12 7:25 ` KOSAKI Motohiro
2011-05-24 20:07 ` Andrew Morton
2011-05-24 20:24 ` David Rientjes [this message]
2011-05-24 20:37 ` Dave Hansen
2011-04-13 0:22 ` David Rientjes
2011-04-13 0:49 ` Dave Hansen
2011-04-13 0:56 ` David Rientjes
2011-04-13 0:16 ` David Rientjes
2011-04-13 0:26 ` Rob Mueller
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.2.00.1105241311260.14396@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dave@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lcm@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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