From: Andi Kleen <ak@suse.de>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Christoph Lameter <clameter@sgi.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: Question: new bind_zonelist uses only one zone type
Date: Tue, 17 Jan 2006 15:29:53 +0100 [thread overview]
Message-ID: <200601171529.53811.ak@suse.de> (raw)
In-Reply-To: <43CCAEEF.5000403@jp.fujitsu.com>
On Tuesday 17 January 2006 09:46, KAMEZAWA Hiroyuki wrote:
> policy_zone is ZONE_DMA, ZONE_NORMAL, ZONE_HIGHMEM, depends on system.
>
> If policy_zone is ZONE_NORMAL, returned zonelist will be
> {Node(0)'s NORMAL, Node(1)'s NORMAL, Node(2)'s Normal.....}
>
> If node0 has only DMA/DMA32 and Node1-NodeX has Normal, node0 will be ignored
> and zonelist will include not-populated zone.
>
> Is this intended ?
I was wondering when someone else would notice. Congratulations, you
are the first ;-)
It was originally intended - back then either IA64 NUMA systems didn't
have a ZONE_DMA and on x86-64 it was only 16MB and for i386 NUMA
it was considered acceptable - and it made the code simpler and policies
use less memory. But is now considered a bug because of the introduction
of ZONE_DMA32 on x86-64 and I gather from your report your platform
has NUMA and a 4GB ZONE_DMA too?
It is on my todo list to fix, but I haven't gotten around to it yet.
Fixing it will unfortunately increase the footprint of the policy structures,
so likely it would only increase to two. If someone beats me to a patch
that would be ok too.
-Andi
--
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:[~2006-01-17 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 8:46 Question: new bind_zonelist uses only one zone type KAMEZAWA Hiroyuki
2006-01-17 14:29 ` Andi Kleen [this message]
2006-01-17 23:47 ` KAMEZAWA Hiroyuki
2006-01-18 3:00 ` Andi Kleen
2006-01-18 3:26 ` KAMEZAWA Hiroyuki
2006-01-18 3:40 ` Jack Steiner
2006-01-18 3:49 ` Andi Kleen
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=200601171529.53811.ak@suse.de \
--to=ak@suse.de \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.