From: Andi Kleen <andi@firstfloor.org>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Tharindu Rukshan Bamunuarachchi <btharindu@gmail.com>,
Tim Pepper <lnxninja@linux.vnet.ibm.com>,
linux-numa@vger.kernel.org
Subject: Re: NUMA page allocation from next Node
Date: Mon, 1 Nov 2010 19:00:59 +0100 [thread overview]
Message-ID: <20101101180059.GJ25817@basil.fritz.box> (raw)
In-Reply-To: <1288623553.3229.24.camel@useless.localdomain>
> Because the SLIT on the IBM platform has distances > 20. Looks like IBM
> is populating the SLIT on those platforms with "real" values. The HP
> bios is not supplying a slit, letting the remote distances default to
> 20. That is the threshold for setting zone_reclaim_mode. A patch was
> submitted recently to bump the threshold to ~30. Now that vendors are
> starting to populate the SLIT with values > 20, we've begun to see the
> behavior that you experienced.
I think it's intentional by the vendors: they use it a way to make
Linux behave like they want.
-Andi
next prev parent reply other threads:[~2010-11-01 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 16:27 NUMA page allocation from next Node Tharindu Rukshan Bamunuarachchi
[not found] ` <20101027213652.GA12345@sgi.com>
2010-10-29 2:05 ` Tharindu Rukshan Bamunuarachchi
[not found] ` <20101029033058.GB555@www.lurndal.org>
2010-10-29 6:58 ` Tharindu Rukshan Bamunuarachchi
[not found] ` <AANLkTikDtKc7RdAWJagqCf7T0JKscfe0Hd0ojc8g7yYo@mail.gmail.com>
2010-10-29 7:06 ` Tharindu Rukshan Bamunuarachchi
2010-10-29 8:49 ` Andi Kleen
2010-10-29 9:16 ` Tharindu Rukshan Bamunuarachchi
2010-10-29 19:52 ` Tim Pepper
2010-10-29 20:30 ` Lee Schermerhorn
2010-11-01 13:55 ` Tharindu Rukshan Bamunuarachchi
2010-11-01 14:18 ` Tharindu Rukshan Bamunuarachchi
2010-11-01 14:59 ` Lee Schermerhorn
2010-11-01 18:00 ` Andi Kleen [this message]
2010-11-02 0:49 ` Tharindu Rukshan Bamunuarachchi
2010-11-01 17:59 ` 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=20101101180059.GJ25817@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=Lee.Schermerhorn@hp.com \
--cc=btharindu@gmail.com \
--cc=linux-numa@vger.kernel.org \
--cc=lnxninja@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).