From: Christoph Lameter <clameter@sgi.com>
To: pj@sgi.com
Cc: ak@suse.de, linux-mm@kvack.org, akpm@osdl.org
Subject: Re: Radical idea
Date: Sun, 17 Sep 2006 06:01:18 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0609170543590.14541@schroedinger.engr.sgi.com> (raw)
Sorry about the wrong email address. Bouncing does not do proper outgoing
address translation.
> Andi wrote:
> > x86-64 can have multiple zones in node > 0 (e.g. node 1 can have both
> > DMA32 and NORMAL)
>In this case, Christoph, would your radical idea preserve user visible
>node numbers? In general, the kernels numbering of nodes (as well as
>its numbering of cpus) is exposed to user space in various ways. What's
>exposed should not change.
It would just add new node numbers for containers and dma zones outside
of the physical range.
And yes it would only work the DMA32 problems mentioned by Andi could be
addressed. Do we really need DMA32 in modern systems with IOMMUs? Isnt
this a transitionary problem that will go away?
So lets say we have one of those systems without IOMMU. Then we only have
a problem for a class of NUMA systems that have:
1. Memory beyond 4GB
and
2. Per node memory less than 4GB. Otherwise DMA32 is only on node 0.
Isnt this a fairly small group of systems?
--
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 reply other threads:[~2006-09-17 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 13:01 Christoph Lameter [this message]
2006-09-17 13:20 ` Paul Jackson
2006-09-17 18:13 ` 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=Pine.LNX.4.64.0609170543590.14541@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=pj@sgi.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