🚀 go-pugleaf

Time to consider following-up to comp.unix.wizards ...

In article <567@jc3b21.UUCP> crash@jc3b21.UUCP (Frank J. Edwards) writes:
>>     while(p!= NULL) { free(p); p = p->next; }

>Ahem, ... I'm probably going to be shot for this, but:  only expect that
>behaviour on a BSD-like UN*X system.  As I understand it, BSD does not
>return free'd memory (as in the sbrk() system call) back to the system.

I don't know of any malloc() implementation for Unix that gives back
freed memory.  It is just assumed that either the program will malloc
it again or that those pages will be paged out by the OS.  This is
almost always a reasonable thing to do.

(A Unix program which is permanently freeing a large chunk of memory
probably should have gotten it via sbrk() in the first place, and can
attempt to free it in the same way.  This similarly applies to Amiga
programs with respect to malloc() vs. AllocMem(), especially considering
that there is very little overhead involved in AllocMem compared to a
Unix system call.)

>System V machines, however, actually remove those memory pages from
>the tasks allocation tables -- the memory is GONE!

This is not true with the supplied malloc libraries.  Such a library
could be written, but I doubt it would be of much use, for reasons
that are not really related to comp.sys.amiga.* subject matter.
-- 
					-=] Ford [=-

"The number of Unix installations	(In Real Life:  Mike Ditto)
has grown to 10, with more expected."	ford@kenobi.cts.com
- The Unix Programmer's Manual,		...!sdcsvax!crash!elgar!ford
  2nd Edition, June, 1972.		ditto@cbmvax.commodore.com