Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!udel!mmdf
From: MDOELL%DOSUNI1.BITNET@cunyvm.cuny.edu (Magnus Doell)
Newsgroups: comp.os.minix
Subject: Re: Huge cache under Minix-32
Message-ID: <32738@nigel.ee.udel.edu>
Date: 8 Oct 90 11:51:13 GMT
Sender: mmdf@ee.udel.edu
Lines: 15


Couldn't we avoid the cache to be build into the image?
As we have vm with the 386, why don't use it to fill the memory
used by FS' cache during initialization?
If we make the initialization a little bit trickier, we could avoid
to build in nearly all the bss by just copying the data regions a
little bit.
By the way, I had read about a project with a 2-stage FS-cache a while
ago (I guess they wanted the second cache dynamically allocated outside
FS' address space). What's about this?
All this makes the image a little bit smaller, the loading a little bit
faster and the initialization a little bit trickier and slower (but you
can copy a lot of memory before reading one sector :-).

Ma.D.