From: Christoph Lameter <clameter@sgi.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
ak@suse.de, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, Eric Whitney <eric.whitney@hp.com>
Subject: Re: [PATCH] change global zonelist order on NUMA v3
Date: Thu, 26 Apr 2007 09:36:40 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704260934430.22248@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1177604962.5705.55.camel@localhost>
On Thu, 26 Apr 2007, Lee Schermerhorn wrote:
> I have been considering an HP-platform-specific boot option [handled by
> a new ia64 machine vec op] to re-distance the interleaved node, but for
> other platforms, such as Kame's, I think we still need the ability to
> move the DMA zones last in the Normal zone lists. Or, exclude them
> altogether?
Maybe a solution would be to have a dma_penalty option on boot? The dma
penalty is added to the dma zone. If its higher than zero then the dma
zone will become a node at that distance to other nodes.
The default is zero which would leave it as is.
If you boot with
dma_penalty=40
then a new slit entry is generated for the DMA zone and its put at that
distance.
--
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>
next prev parent reply other threads:[~2007-04-26 16:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 9:34 [PATCH] change global zonelist order on NUMA v2 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 [this message]
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
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.0704260934430.22248@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=eric.whitney@hp.com \
--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