Mail Archives: djgpp/1994/01/08/17:15:32
> 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.)
- Raw text -