From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: sparsemem & sparsemem extreme question
Date: Wed, 5 Oct 2005 19:45:42 +0200 [thread overview]
Message-ID: <20051005174542.GB10204@osiris.ibm.com> (raw)
In-Reply-To: <1128532809.26009.39.camel@localhost>
> > Anything specific you need to know about the memory layout?
> How sparse is it? How few present pages can be there be in a worst-case
> physical area?
Worst case that is already currently valid is that you can have 1 MB
segments whereever you want in address space.
For instance I just configured a virtual machine that has the following
memory layout:
Address Range
-----------------------------------
0000000000000000 - 00000000000FFFFF
000000FFC0000000 - 000000FFC00FFFFF
Even though it's currently not possible to define memory segments above
1TB, this limit is likely to go away.
In addition if running in a logical partition we always have a small gap
at the 2GB barrier. Not sure how large that gap is, I'll check tomorrow.
Heiko
--
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:[~2005-10-05 17:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 6:50 sparsemem & sparsemem extreme question Heiko Carstens
2005-10-04 14:33 ` Andy Whitcroft
2005-10-04 16:15 ` Dave Hansen
2005-10-05 6:39 ` Heiko Carstens
2005-10-05 15:52 ` Dave Hansen
2005-10-05 15:58 ` Heiko Carstens
2005-10-05 16:05 ` Dave Hansen
2005-10-05 16:10 ` Heiko Carstens
2005-10-05 16:20 ` Dave Hansen
2005-10-05 17:12 ` Heiko Carstens
2005-10-05 17:20 ` Dave Hansen
2005-10-05 17:45 ` Heiko Carstens [this message]
2005-10-05 17:57 ` Dave Hansen
2005-10-05 18:04 ` Heiko Carstens
2005-10-05 18:42 ` Bob Picco
2005-10-05 22:06 ` Dave Hansen
2005-10-06 7:39 ` Heiko Carstens
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=20051005174542.GB10204@osiris.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=haveblue@us.ibm.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.