From: David Edelsohn <dje@watson.ibm.com>
To: Dan Malek <dan@mvista.com>
Cc: Roman Zippel <zippel@fh-brandenburg.de>,
mgreer@mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: CONFIG_HIGHMEM on PPC
Date: Thu, 25 Jan 2001 14:59:06 -0500 [thread overview]
Message-ID: <200101251959.OAA27790@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Dan Malek <dan@mvista.com> of "Thu, 25 Jan 2001 14:47:43 EST." <3A7082DF.CD7E8B61@mvista.com>
>>>>> Dan Malek writes:
Dan> Heh....64Gbyte is nothing, just a few more bits beyond 32....you
Dan> don't need 64-bits for this. In fact, I had a revelation last
Dan> night where I thought we could even do this quite transparently
Dan> on PowerPCs with VSIDs or even context registers, anything that
Dan> implictly gives us a few more bits of virtual address. Later
Dan> on that.....
Yes, that is the exact purpose of the PowerPC addressing model.
While one user context is limited to 32-bit addresses, the system can map
a larger physical address range into the process's virtual address space.
The process even could handle this with OS cooperation using overlays.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-25 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 0:31 CONFIG_HIGHMEM on PPC Mark A. Greer
2001-01-25 6:04 ` Dan Malek
2001-01-25 6:44 ` HTTP daemon required Srinivas Rao.M
2001-01-25 9:25 ` CONFIG_HIGHMEM on PPC Roman Zippel
2001-01-25 17:08 ` Dan Malek
2001-01-25 18:37 ` Roman Zippel
2001-01-25 19:47 ` Dan Malek
2001-01-25 19:59 ` David Edelsohn [this message]
2001-01-25 21:36 ` Roman Zippel
2001-01-25 21:51 ` Gabriel Paubert
2001-01-25 22:35 ` Roman Zippel
2001-01-25 22:39 ` David Edelsohn
2001-01-26 3:05 ` Frank Rowand
2001-01-25 19:28 ` Gabriel Paubert
2001-01-25 20:07 ` Dan Malek
2001-01-25 21:40 ` Gabriel Paubert
2001-01-25 21:46 ` David Edelsohn
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=200101251959.OAA27790@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=dan@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mgreer@mvista.com \
--cc=zippel@fh-brandenburg.de \
/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;
as well as URLs for NNTP newsgroup(s).