From: Jack Steiner <steiner@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
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 21:40:03 -0600 [thread overview]
Message-ID: <20060118034003.GA1300@sgi.com> (raw)
In-Reply-To: <200601180400.41448.ak@suse.de>
On Wed, Jan 18, 2006 at 04:00:41AM +0100, Andi Kleen wrote:
> On Wednesday 18 January 2006 00:47, KAMEZAWA Hiroyuki wrote:
> > Andi Kleen wrote:
> > > 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?
> >
> > on ia64, 0-4G area is ZONE_DMA.
>
> On IA64/SN2 ZONE_DMA is empty and at least in the part SGI was the only
> IA64 vendor actively interested in NUMA policy.
>
On the SN systems, ALL memory is in the DMA zone. The other zones are empty.
I think this is SN-specific - other IA64 platforms may be different & have memory
in multiple zones.
--
Jack
--
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-18 3:40 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
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 [this message]
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=20060118034003.GA1300@sgi.com \
--to=steiner@sgi.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox