On 2013-08-16 09:42, Geert Uytterhoeven wrote:
IIRC, Linux itself now also has a software variant of the SSD hybrid
disk approach.
So we could use that on a RAM block device instead of an SSD.
Still we would have the additional layer and workload of swapping. I
think that approach is fairly ok as a quick solution to get the
BigRamPlus working, but it seems to me that the setup will be somewhat
awkward... ;)
Remember that there were problems with loading 3.2.0-4-amiga without
the memfile.
Yes, going out of memory when allocating the page table arrays? That
won't
improve when adding 256 MiB of Z3 RAM in the far end of the physical
address space...
No, but we would have more memory to waste for this. Excluding 8 MB
for this from 128 MB does hurt more than 8 MB out of 384 MB. ;)
I mean that we would waste more memory too, due to the Z3 RAM being far
from
the rest of RAM in the address space.
Can't the MMU map the memory as needed?
--
Ciao... // Fon: 0381-2744150
. Ingo \X/ http://blog.windfluechter.net
gpg pubkey: http://www.juergensmann.de/ij_public_key.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/4f61ed7088bb5d7cddefd0456360c615@localhost
