Thanks David for your msg about 512mb Is Ample Right Now, on 08
10-08-1994

DN> complete file mapping simply because the buffer lookasides on
DN> a full file mapping scheme would cause excessive page faults.
DN> Even with sparse page-frame allocation, as soon as a page-frame
DN> is referenced it must be committed. If this can cause problems
DN> on a 10GB mainframe with 500TB of 

But, OS/2 allows you to decommit page, which would give back the
physical memory and 'reset' the fault in of the pages? I've used
sparse allocation but I haven't had a need to decommit so I'm not
for sure if it's doable. So the exception handler would be able to
use an LRU algorithm to decommit old pages and map new ones in. So
the a single 64Meg (for instance) block could continually be used
to manage a file of any size without the physical memory
commitment growing cancerously (is that a word?.)

___
 X KWQ/2 1.2b X This tagline stolen by KWQ Mail/2.

--- Maximus/2 2.01wb