🚀 go-pugleaf

In article <3009@amiga.UUCP> jimm@amiga.UUCP (Jim Mackraz) writes:

>By the way: memory fragmentation on the Amiga occurs because there are
>actually allocated sections of memory between the freed chunks.  There's
>been a lot of discussion on this already.
>
>Note that you can't concatenate two non-adjacent chunks.

Ah.  So what we need is an MMU (i.e. virtual memory).

Hmmm.  What would happen if the ALLOCATE and DEALLOCATE functions were
re-written in such a way that all memory would be allocated in 1k chunks?
Then successive calls to ALLOCATE would check to see if part of an
already-allocated chunk was available for allocation, and use that if it
could.

That is, first call (100 bytes) results in a 1k chunk being allocated. 
Second call results in a second pointer into the same 1k chunk.  This might
reduce the problem you spoke of without as much need to resort to an MMU.

If we could keep track of all pointers to a memory chunk, we could
rearrange them no problem.  But then the Amiga OS isn't quite *that*
object-oriented.


Dan Hankins