From: David Rientjes <rientjes@google.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Anton Blanchard <anton@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ppc: RECLAIM_DISTANCE 10?
Date: Wed, 19 Feb 2014 00:20:21 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1402190017480.7280@chino.kir.corp.google.com> (raw)
In-Reply-To: <20140219081644.GA14783@dhcp22.suse.cz>
On Wed, 19 Feb 2014, Michal Hocko wrote:
> > I strongly suspect that the patch is correct since powerpc node distances
> > are different than the architectures you're talking about and get doubled
> > for every NUMA domain that the hardware supports.
>
> Even if the units of the distance is different on PPC should every NUMA
> machine have zone_reclaim enabled? That doesn't right to me.
>
In my experience on powerpc it's very correct, there's typically a
significant latency in remote access and we don't have the benefit of a
SLIT that actually defines the locality between proximity domains like we
do on other architectures. We have had significant issues with thp, for
example, being allocated remotely instead of pages locally, much more
drastic than on our x86 machines, particularly AMD machines.
--
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>
next prev parent reply other threads:[~2014-02-19 8:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 9:06 Michal Hocko
2014-02-18 22:27 ` David Rientjes
2014-02-19 8:16 ` Michal Hocko
2014-02-19 8:20 ` David Rientjes [this message]
2014-02-19 9:19 ` Michal Hocko
2014-02-19 21:45 ` David Rientjes
2014-02-18 23:34 ` Nishanth Aravamudan
2014-02-18 23:58 ` Nishanth Aravamudan
2014-02-19 0:40 ` Nishanth Aravamudan
2014-02-19 1:43 ` David Rientjes
2014-02-19 8:33 ` Michal Hocko
2014-02-19 16:24 ` Nishanth Aravamudan
2014-02-19 16:33 ` Nishanth Aravamudan
2014-02-20 9:55 ` Michal Hocko
2014-02-19 8:23 ` Michal Hocko
2014-02-19 16:26 ` Nishanth Aravamudan
2014-02-19 17:03 ` [RFC PATCH] mm: exclude memory less nodes from zone_reclaim Michal Hocko
2014-02-19 17:16 ` Nishanth Aravamudan
2014-02-19 17:32 ` Michal Hocko
2014-02-19 17:49 ` Nishanth Aravamudan
2014-02-19 19:40 ` Michal Hocko
2014-02-19 17:53 ` Nishanth Aravamudan
2014-02-19 21:56 ` David Rientjes
2014-02-19 23:05 ` Nishanth Aravamudan
2014-02-20 9:50 ` Michal Hocko
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.02.1402190017480.7280@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.cz \
/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