linux-numa.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Tharindu Rukshan Bamunuarachchi <btharindu@gmail.com>
Cc: jiahua@gmail.com, Cliff Wickman <cpw@sgi.com>,
	linux-numa@vger.kernel.org
Subject: Re: NUMA page allocation from next Node
Date: Fri, 29 Oct 2010 10:49:15 +0200	[thread overview]
Message-ID: <20101029084915.GD11149@basil.fritz.box> (raw)
In-Reply-To: <AANLkTikNckdZ=P=-KnNt=tD4md-5pCr0KbK8yd9AzNvU@mail.gmail.com>

On Fri, Oct 29, 2010 at 12:36:47PM +0530, Tharindu Rukshan Bamunuarachchi wrote:
> What kind of NUMA setting i should look for ? I gather following config values ?

Most likely one of the systems forces zone reclaim by having large
SLIT values and the other doesn't. You can configure zone reclaim
manually through sysctl.

You should not get a lockup though in any case, that's some kind of 
VM bug in 2.6.27. I would recommend reporting that to Novell.

-Andi

  reply	other threads:[~2010-10-29  8:49 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 [this message]
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
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=20101029084915.GD11149@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=btharindu@gmail.com \
    --cc=cpw@sgi.com \
    --cc=jiahua@gmail.com \
    --cc=linux-numa@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;
as well as URLs for NNTP newsgroup(s).