linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Christoph Lameter <clameter@sgi.com>,
	ak@suse.de, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org, mike.stroyan@hp.com
Subject: Re: [PATCH] change global zonelist order on NUMA v2
Date: Mon, 30 Apr 2007 10:09:48 -0400	[thread overview]
Message-ID: <1177942188.5623.8.camel@localhost> (raw)
In-Reply-To: <20070427092736.d0626a30.kamezawa.hiroyu@jp.fujitsu.com>

On Fri, 2007-04-27 at 09:27 +0900, KAMEZAWA Hiroyuki wrote:
> On Thu, 26 Apr 2007 08:48:19 -0700 (PDT)
> Christoph Lameter <clameter@sgi.com> wrote:
> 
> > On Thu, 26 Apr 2007, KAMEZAWA Hiroyuki wrote:
> > 
> > > (1)Use new zonelist ordering always and move init_task's tied cpu to a
> > >   cpu on the best node. 
> > >   Child processes will start in good nodes even if Node 0 has small memory.
> > 
> > How about renumbering the nodes? Node 0 is the one with no DMA memory and 
> > node 1 may be the one with the DMA? That would take care of things even 
> > without core modifications. We can start on node 0 (which hardware 1) and 
> > consume the required memory for boot there not impacting the node with the 
> > DMA memory.
> > 
> It seems a bit complicated. If we do so, following can occur,
> 
> Node1: cpu0,1,2,3
> Node0: cpu4,5,6,7
> 
> the system layout will be not imaginable look, maybe.

Interesting.  A colleague recently showed me that this can occur on HP
platforms if we boot from, say, node 1 instead of node 0.  The kernel
doesn't mind because it maintains a translation of cpus to nodes and
vice versa.  Applications don't need to mind if they use libnuma's
numa_node_to_cpus(), rather than assume a fixed relationship.  But, I
agree, that it may surprise some people when/if node_id !=
cpu_id/cpus_per_node.

Lee

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

  parent reply	other threads:[~2007-04-30 14:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26  9:34 KAMEZAWA Hiroyuki
2007-04-26  9:47 ` Andi Kleen
2007-04-26 10:10   ` KAMEZAWA Hiroyuki
2007-04-26 10:53     ` [PATCH] change global zonelist order on NUMA v3 KAMEZAWA Hiroyuki
2007-04-26 16:00       ` Lee Schermerhorn
2007-04-26 16:06         ` Christoph Lameter
2007-04-26 16:29           ` Lee Schermerhorn
2007-04-26 16:36             ` Christoph Lameter
2007-04-26 15:48     ` [PATCH] change global zonelist order on NUMA v2 Christoph Lameter
2007-04-27  0:27       ` KAMEZAWA Hiroyuki
2007-04-27  1:25         ` Christoph Lameter
2007-04-27  1:50           ` KAMEZAWA Hiroyuki
2007-04-30 15:03           ` Lee Schermerhorn
2007-04-30 14:09         ` Lee Schermerhorn [this message]
2007-04-26 15:46   ` Christoph Lameter
2007-04-26 15:51     ` Andi Kleen
2007-04-26 21:57 ` Lee Schermerhorn
2007-04-26 22:07   ` Christoph Lameter
2007-04-27  0:41   ` 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=1177942188.5623.8.camel@localhost \
    --to=lee.schermerhorn@hp.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.stroyan@hp.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