At 01:22 PM 4/5/98 -0700, David Greenman wrote:
>>while. It's simply a *lot* faster to keep already-linked executables
>>in memory (and move them into swap when memory goes full) rather than
>>throwing them out and having to reload and relink them next time they
>>are invoked, as long as they haven't changed in the meantime.
>>David, I hope my explanation is not too far off?
> Actually, it's not that the system has to do any re-linking. The reason
>that swap space is consumed even when you have plenty of memory is that the
>system also tries to cache regular file data, so freeing up memory for that
>by moving modified but not recently used process pages to swap is usually a
My only quibble with this technique is that it would seem to make it
harder to tell if your machine is really running low on swap or not
(e.g. swap as backing store for stack/heap/whatever *is* critical and
allocation failure can cause application failure, whereas swap being
used to cache random cruft is in the "who really cares" department).
Or is there some way to tell the difference?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message