From: Christoph Lameter <clameter@sgi.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>, GOTO <y-goto@jp.fujitsu.com>
Subject: Re: [RFC][PATCH] syctl for selecting global zonelist[] order
Date: Wed, 25 Apr 2007 12:17:15 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704251211070.17886@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070425121946.9eb27a79.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, 25 Apr 2007, KAMEZAWA Hiroyuki wrote:
> Make zonelist policy selectable from sysctl.
>
> Assume 2 node NUMA, only node(0) has ZONE_DMA (ZONE_DMA32).
>
> In this case, default (node0's) zonelist order is
>
> Node(0)'s NORMAL -> Node(0)'s DMA -> Node(1)"s NORMAL.
>
> This means Node(0)'s DMA is used before Node(1)'s NORMAL.
So a IA64 platform with i386 sicknesses? And pretty bad case of it since I
assume that the memory sizes per node are equal. Your solution of taking
4G off node 0 and then going to node 1 first must hurt some
processes running on node 0. But there is no easy solution since
the hardware is badly screwed up with 32 bit I/O. Whatever you do the
memory balance between the two nodes is making the system behave in
an unsymmetric way.
> In some server, some application uses large memory allcation.
> This exhaust memory in the above order.
Could we add a boot time option instead that changes the zonelist build
behavior? Maybe an arch hook that can deal with it?
--
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-25 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 3:19 KAMEZAWA Hiroyuki
2007-04-25 7:42 ` Andrew Morton
2007-04-25 7:55 ` KAMEZAWA Hiroyuki
2007-04-25 9:31 ` Andi Kleen
2007-04-25 19:17 ` Christoph Lameter [this message]
2007-04-26 0:31 ` KAMEZAWA Hiroyuki
2007-04-26 0:40 ` 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.0704251211070.17886@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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