From: Dave Hansen <haveblue@us.ibm.com>
To: "Mika Penttilä" <mika.penttila@kolumbus.fi>
Cc: Andy Whitcroft <apw@shadowen.org>,
lhms <lhms-devel@lists.sourceforge.net>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [Lhms-devel] Re: 150 nonlinear
Date: Tue, 26 Oct 2004 14:27:03 -0700 [thread overview]
Message-ID: <1098826023.7172.4.camel@localhost> (raw)
In-Reply-To: <417EBFB3.5000803@kolumbus.fi>
On Tue, 2004-10-26 at 14:20, Mika Penttila wrote:
> "There are two problems that are being solved: having a sparse layout
> requiring splitting up mem_map (solved by discontigmem and your
> nonlinear), and supporting non-linear phys to virt relationships (Dave
> M's implentation which does the mem_map split as well)."
>
>
> so what's the split?
So, mem_map is normally laid out so that, if you have 1GB of memory, the
memory for 0x00000000 is at mem_map[0], and the memory for the last page
(at 1GB - 1 page) is at mem_map[1<<30 / PAGE_SIZE - 1].
That's fine and dandy for most systems. But, imagine that you have some
memory on a funky machine where you have 2GB of memory, but it is laid
out like this:
0-1 GB - first 1 GB
1-100 GB - empty
100-101 GB - second 1 GB
Then, you'd need to have mem_map sized the same as a 101GB system on
your dinky 2GB system (disregard the ia64 implementation).
The split I'm referring to is cutting mem_map[] up into pieces for each
contiguous section of memory.
Make sense?
-- Dave
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-10-26 21:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 14:24 CONFIG_NONLINEAR for small systems Andy Whitcroft
2004-10-18 14:32 ` 050 bootmem use NODE_DATA Andy Whitcroft
2004-10-26 18:16 ` Dave Hansen
2004-10-18 14:33 ` 060 refactor setup_memory i386 Andy Whitcroft
2004-10-18 14:34 ` 080 alloc_remap i386 Andy Whitcroft
2004-10-18 14:35 ` 100 cleanup node zone Andy Whitcroft
2004-10-18 14:35 ` 150 nonlinear Andy Whitcroft
2004-10-26 18:36 ` Dave Hansen
2004-10-26 19:07 ` [Lhms-devel] " Mika Penttilä
2004-10-26 19:42 ` Dave Hansen
2004-10-26 20:41 ` Mika Penttilä
2004-10-26 20:55 ` Dave Hansen
2004-10-26 21:20 ` Mika Penttilä
2004-10-26 21:27 ` Dave Hansen [this message]
2004-10-26 21:38 ` Mika Penttilä
2004-10-26 21:41 ` Dave Hansen
2004-10-26 21:55 ` Mika Penttilä
2004-10-26 21:53 ` Dave Hansen
2004-10-26 22:01 ` Mika Penttilä
2004-10-28 11:07 ` Andy Whitcroft
2004-10-18 14:36 ` 160 nonlinear i386 Andy Whitcroft
2004-10-18 14:36 ` 170 nonlinear ppc64 Andy Whitcroft
2004-10-18 15:17 ` [Lhms-devel] CONFIG_NONLINEAR for small systems Hirokazu Takahashi
2004-10-18 15:29 ` Andy Whitcroft
2004-10-19 4:30 ` Hiroyuki KAMEZAWA
2004-10-19 8:16 ` Andy Whitcroft
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=1098826023.7172.4.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=apw@shadowen.org \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=mika.penttila@kolumbus.fi \
/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