Xref: utzoo comp.sys.ibm.pc:28515 comp.sys.amiga:33500
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!oliveb!amiga!boing!dale
From: dale@boing.UUCP (Dale Luck)
Newsgroups: comp.sys.ibm.pc,comp.sys.amiga
Subject: Re: OS/2 vs AmigaDOS
Message-ID: <746@boing.UUCP>
Date: 9 May 89 15:00:17 GMT
References: <5664@microsoft.UUCP> <6793@cbmvax.UUCP>
Reply-To: dale@boing.UUCP (Dale Luck)
Organization: Boing, Milpitas, Ca.
Lines: 26

In article <6793@cbmvax.UUCP> daveh@cbmvax.UUCP (Dave Haynie) writes:
>
>Amiga shared libraries, fonts, and device drivers are all demand-loaded.  Any
>more sophisticated form of demand loading should be, IMHO, based on a hardware
>driven virtual memory manager.  If you haven't isolated the things that are
>to be loaded on demand, you're going to be pretty inefficient it would seem.
>And without any obvious indication of useage, such as in an Amiga device or
>font, or a VM manager's page count tags, the system isn't going to know enough
>to unload stuff that hasn't been recently used, at least not without some 
>serious software overhead.  
>

I think we could granularize the demand loading a bit further. When a
demand loaded library is opened it presently loads all the functions.
We could instead just load stubs that would then load individual
functions as they are actually used. I think this would save alot on
memory since many functions are not even used in these libraries.

In the instance of the ieee transcendental library, they most used
function is sqrt, the hyperbolic cosines just are not used that often. ;+)

I'm sure this is true for most demand loaded libraries.

-- 
Dale Luck     GfxBase/Boing, Inc.
{uunet!cbmvax|pyramid}!amiga!boing!dale