From: Frank Rowand <frank_rowand@mvista.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Gabriel Paubert <paubert@iram.es>, Dan Malek <dan@mvista.com>,
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 19:05:55 -0800 [thread overview]
Message-ID: <3A70E993.54149F46@mvista.com> (raw)
In-Reply-To: 200101252239.RAA04412@mal-ach.watson.ibm.com
David Edelsohn wrote:
>
> >>>>> Gabriel Paubert writes:
>
> Gabriel> BATS are a good idea, but variable page size are another, superior IMHO,
> Gabriel> possibility. It seems to be what Power4 has from what David said a few
> Gabriel> days ago. I don't know how they mix variable page size with hash tables
> Gabriel> and failed to find any detailed documentation...
>
> The variable page sizes are determined on a segment by segment
> basis. The segment type determines how to interpret the page table --
> whether it maps 4KB or 16MB.
The 405 processors have page sizes of
1k
4k
16k
64k
256k
1m
4m
16m
The 440 processors are the same except
4m removed
256m added
The page size is determined by a field in the TLB entry.
-Frank
--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-26 3:05 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 [this message]
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=3A70E993.54149F46@mvista.com \
--to=frank_rowand@mvista.com \
--cc=dan@mvista.com \
--cc=dje@watson.ibm.com \
--cc=frowand@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.