From: Dave Hansen <haveblue@us.ibm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: sparsemem & sparsemem extreme question
Date: Wed, 05 Oct 2005 09:20:22 -0700 [thread overview]
Message-ID: <1128529222.26009.16.camel@localhost> (raw)
In-Reply-To: <20051005161009.GA10146@osiris.ibm.com>
On Wed, 2005-10-05 at 18:10 +0200, Heiko Carstens wrote:
> > > No, my concern is actually that the s390 archticture actually will come up
> > > with some sort of memory that's present in the physical address space where
> > > the most significant bit of the addresses will be turned _on_.
> >
> > Why do you think this?
>
> That's a matter of fact and what the Specs say...
I'd appreciate any pointer to the relevant information, especially the
stuff that explains just how sparse a physical address space can be on
that architecture. What would discontigmem have done with the same
layout? Does s390 even support discontigmem?
-- 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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-10-05 16:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 6:50 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 [this message]
2005-10-05 17:12 ` Heiko Carstens
2005-10-05 17:20 ` Dave Hansen
2005-10-05 17:45 ` Heiko Carstens
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=1128529222.26009.16.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=heiko.carstens@de.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox