From: Christoph Lameter <clameter@sgi.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] change global zonelist order on NUMA v2
Date: Thu, 26 Apr 2007 08:48:19 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704260846590.1382@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070426191043.df96c114.kamezawa.hiroyu@jp.fujitsu.com>
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.
next prev parent reply other threads:[~2007-04-26 15:48 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 ` Christoph Lameter [this message]
2007-04-27 0:27 ` [PATCH] change global zonelist order on NUMA v2 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
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=Pine.LNX.4.64.0704260846590.1382@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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
all inboxes | Powered by JetHome®