From: Bob Picco <bob.picco@hp.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Dave Hansen <haveblue@us.ibm.com>, linux-mm <linux-mm@kvack.org>,
Bob Picco <bob.picco@hp.com>
Subject: Re: sparsemem & sparsemem extreme question
Date: Wed, 5 Oct 2005 14:42:54 -0400 [thread overview]
Message-ID: <20051005184254.GA25483@localhost.localdomain> (raw)
In-Reply-To: <20051005180443.GC10204@osiris.ibm.com>
Heiko Carstens wrote: [Wed Oct 05 2005, 02:04:43PM EDT]
> > > > > 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.
> > ...
> > > Even though it's currently not possible to define memory segments above
> > > 1TB, this limit is likely to go away.
> >
> > Go away, or get moved up?
> >
> > ia64 today is designed to work with 50 bits of physical address space,
> > and 30 bit sections. That's exactly the same scale that you're talking
> > about with 1MB sections and 1TB of physical space. So, sparsemem
> > extreme should be perfectly fine for that case (that's explicitly what
> > it was designed for).
> >
> > How much bigger than 1TB will it go?
>
> As already mentioned, we will have physical memory with the MSB set. Afaik
> the hardware uses this bit to distinguish between different types of memory.
> So we are going to have the full 64 bit address space.
>
> Heiko
Possibly the architects did a similar thing to ia64. When bit 63 is set the
access in uncached. This doesn't seem relevant to sparsemem. The attribute
could be stored in page structure flags or some other way.
bob
--
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 18:42 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
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 [this message]
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=20051005184254.GA25483@localhost.localdomain \
--to=bob.picco@hp.com \
--cc=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