Date: Sat, 8 Jan 94 16:59:25 EST
From: peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: Mail Delivery Subsystem
Reply-To: babcock AT cfa DOT harvard DOT edu

> But what if you're writing a time-critical application and your algorithm
> can cope with less memory at the expense of, say, accuracy? Is there some
> "standard" way of telling the O/S that you only want real (fast) memory and
> not virtual (slow, disk-swapped) memory?

One possibility would be to point go32tmp at a disk (or RAM disk) with no
free space, then carefully monitor available virtual memory and don't do
anything which would trigger swapping.  Sounds dangerous, and I hope that
there is a better way.  _go32_dpmi_get_free_memory_information will return the
available "real" memory in some dpmi environments, but not all.  (It only
returns virtual memory under os/2.)