From: Dan Malek <dan@mvista.com>
To: Gabriel Paubert <paubert@iram.es>
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 15:07:49 -0500 [thread overview]
Message-ID: <3A708795.9D627FE9@mvista.com> (raw)
In-Reply-To: Pine.HPX.4.10.10101251838570.22074-100000@gra-ux1.iram.es
Gabriel Paubert wrote:
> ..... Has anybody
> any docs on how the MMU has been modified to handle the extra bits on the
> 7450.
Yes, I have one and I am working on it. Although I have been spending
time at the lower end of the processor scale, my changes are directly
applicable to the 7450 enhancements as well. Of course, we then
have the "common kernel" problem :-). If I build something to
take advantage of the 7450 enhancements, it may not boot on other
systems.
> The only port which is simple is the 68k
Lots of people complain about it, but I'll agree the 68k MMU
design and supporting instructions is still the best.
> ...... Using such a simple trick for processors which do not allow
> to (easily or not) access alternate address spaces is not an option.
You can easily make the PowerPC have this same alternate address
design. Either people forget or have never known the value of these
large virtual alternate address space designs, and simply jump to
the common space design we have in Linux.
> ............ Now, assuming that you
> can store one bit in one atom of hydrogen, the weight of 2^128 bytes of
> memory would be in the range of a few 10^9 tons, hardly practical for
> mobile systems ;-)
Of course, you know that 1 bits weight more than 0 bits, right? I
proved it once. I wrote a streamer tape with all 0s, weighed it,
then wrote it with all 1s. It weighed slightly more with all 1s :-).
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-25 20:07 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
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 [this message]
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=3A708795.9D627FE9@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mgreer@mvista.com \
--cc=paubert@iram.es \
--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 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.