Date:	08 Jan 94 08:41:19 EST
From:	Peter Linich <100010 DOT 1702 AT CompuServe DOT COM>
To:	<djgpp AT sun DOT soe DOT clarkson DOT edu>
Subject:	Mail Delivery Subsystem

Ok, I've loaded the 1.11 release of djgpp and it all seems to be hunky-dory.

I'm not sure if this is the right place to ask but I have something part
philosophical and part practical to ask.

If you're writing in a VMM operating environment how can you limit the
memory that you get allocated to "real" memory? I'm thinking just from the
C, and not C++, point of view here. In ANSI C there's only free() and
malloc() to handle memory allocations. If you ask for more memory than
"really" exists the VMM clicks in and you cant tell that it has.

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?

In some O/Ses that I've seen you can lock a block of memory (even the
dreaded Windows can do that). Is what I'm asking an O/S question more than a
language question?

The practical thing I want to ask is, is there a way to get go32 to not "go
virtual", to only make available real memory?

- Raw text -