WARNING OFF TOPIC SLIGHTLY: 8xx MMU w/8MB pages

[Dan Malek]

Alan Mimms wrote:


> I would like to suggest that using one or two 512MB pages


That isn't what I would do.  You can map the entire kernel
instruction space with a single 8M entry.  You can map the
entire static data space with another 8M entry.  You can
map frequently used I/O with another 8M data entry.

You have to move the VM map so dynamically allocated data
doesn't overlap the 8M page.  You have to make sure dynamically
loaded modules don't overlap the 8M instruction map.  Or, make
sure they overlap entirely (either way is fine, just don't mix
it up).  You can modify the ioremap() functions to operate more
like they do on the processors with BATs.

All of these are likely to be useful in most applications.  They
don't require any Linux VM or TLB software changes.  All you
need to change are some #define configuration vaules in a couple
of VM/MMU header files and slightly change the MMU initialization.

Maybe I'll do this later today.....I have been thinking about it
long enough.



	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/