mmu.library initialization consumes ~1.5MB?!

[Karlos]

MMU's perform virtual to physical address mapping. They do this using page tables. Those tables are stored in RAM (where else?).

The more RAM you have in your system, the more pages need to be mapped and so the larger the page table gets.

[Karlos]

Hmm.. I have 128MB of fast ram while mike- has 32MB.
If i have understood you correctly, this explains why MMU occupies so much RAM in my case. :-?
 Thanks!

Sounds about right but I'd need to check the exact sizes. 1.5 MB sounds a bit big still for 128MB. 680x0 MMU pages are usually 4KB each (8K is possible on 040/060 IIRC), so that's 32768 pages at 4K each. Now, there are tiers to MMU page tables too, so you have your table of 4K blocks, then a table of 256K blocks (exact size may be different) and so on. The idea is that they exist in a tree like hierarchy to assist address lookup. Even taking these layers into account, I can't see a page table that size needing 1.5MB. Perhaps your kickstart has also been remapped by mmu.library?