linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Miao Xie <miaox@cn.fujitsu.com>, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Christoph Lameter <cl@linux-foundation.org>,
	Paul Menage <menage@google.com>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Yasunori Goto <y-goto@jp.fujitsu.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	David Rientjes <rientjes@google.com>,
	Lee Schermerhorn <lee.schermerhorn@hp.com>,
	linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [BUGFIX] set_mempolicy(MPOL_INTERLEAV) N_HIGH_MEMORY aware
Date: Tue, 28 Jul 2009 19:04:07 +0900 (JST)	[thread overview]
Message-ID: <2c1ca41fbc03aeab347be61920e222b1.squirrel@webmail-b.css.fujitsu.com> (raw)
In-Reply-To: <877hxti405.fsf@basil.nowhere.org>

Andi Kleen wrote:
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
>
>> tested on x86-64/fake NUMA and ia64/NUMA.
>> (That ia64 is a host which orignal bug report used.)
>>
>> Maybe this is bigger patch than expected, but NODEMASK_ALLOC() will be a
>> way
>> to go, anyway. (even if CPUMASK_ALLOC is not used anyware yet..)
>> Kosaki tested this on ia64 NUMA. thanks.
>
> Note that low/high memory support in NUMA policy is only partial
> anyways, e.g. the VMA based policy only supports a single zone. That
> was by design choice and because NUMA has a lot of issues on 32bit due
> to the limited address space and is not widely used.
>
> So small fixes are ok but I wouldn't go to large effort to fix NUMA
> policy on 32bit.
>
ya, maybe you mention to something related to policy_zone.
It's checked only in bind code now. (from before 2.6.30..)
The bug was accessing NODE_DATA(nid), which is NULL.
(All possible node doesn't have pgdat)

Thanks,
-Kame


--
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>

  reply	other threads:[~2009-07-28 10:04 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  9:48 [BUG] set_mempolicy(MPOL_INTERLEAV) cause kernel panic KOSAKI Motohiro
2009-07-15 17:31 ` Lee Schermerhorn
2009-07-16  1:00   ` KOSAKI Motohiro
2009-07-16 20:05   ` David Rientjes
2009-07-17  0:04     ` KOSAKI Motohiro
2009-07-17  0:57       ` KAMEZAWA Hiroyuki
2009-07-17  2:07         ` KOSAKI Motohiro
2009-07-17  2:39           ` KAMEZAWA Hiroyuki
2009-07-17  9:09         ` David Rientjes
2009-07-17  9:01       ` David Rientjes
2009-07-24 22:51     ` David Rientjes
2009-07-24 23:09       ` Andrew Morton
2009-07-25  1:33         ` KAMEZAWA Hiroyuki
2009-07-25  2:35           ` KAMEZAWA Hiroyuki
2009-07-25  3:15             ` KAMEZAWA Hiroyuki
2009-07-25 13:21               ` KOSAKI Motohiro
2009-07-25 14:40                 ` KAMEZAWA Hiroyuki
2009-07-27 18:00                   ` David Rientjes
2009-07-27 17:55               ` David Rientjes
2009-07-27 23:58                 ` KAMEZAWA Hiroyuki
2009-07-28  0:14                   ` David Rientjes
2009-07-28  0:25                     ` KAMEZAWA Hiroyuki
2009-07-28  0:38                       ` David Rientjes
2009-07-28  0:54                         ` KAMEZAWA Hiroyuki
2009-07-28  1:02                           ` David Rientjes
2009-07-28  1:11                             ` KAMEZAWA Hiroyuki
2009-07-28  1:24                               ` KAMEZAWA Hiroyuki
2009-07-28  7:18 ` [BUGFIX] set_mempolicy(MPOL_INTERLEAV) N_HIGH_MEMORY aware KAMEZAWA Hiroyuki
2009-07-28  8:52   ` Andi Kleen
2009-07-28 10:04     ` KAMEZAWA Hiroyuki [this message]
2009-07-29 20:16   ` Andrew Morton
2009-07-30  0:06     ` KAMEZAWA Hiroyuki

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=2c1ca41fbc03aeab347be61920e222b1.squirrel@webmail-b.css.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=cl@linux-foundation.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=menage@google.com \
    --cc=miaox@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=penberg@cs.helsinki.fi \
    --cc=rientjes@google.com \
    --cc=y-goto@jp.fujitsu.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).