Xref: news2.mv.net comp.os.msdos.djgpp:3294
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DPMI paging
Date: Tue, 30 Apr 1996 10:29:39 CDT
Organization: Rice University, Houston, Texas
Lines: 12
Message-ID: <318631e3.sandmann@clio.rice.edu>
References: <9604291657 DOT aa09964 AT ailin DOT inti DOT edu DOT ar> <4m4369$htj AT news DOT wco DOT com>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> I may be completely Bass-Ackwards, but I thought I read somewhere in the
> docs that for performance reasons, the data is not paged out of memory, but
> is marked as pageable so if the spawned proccess actually needs that much
> memory, it can get it.  Am I right?

Actually, nothing is marked as pagable, since it's all pageable by default
unless its marked non-pageable (like interrupt handlers).  Since interrupt
handlers may still be called inside the DJGPP image when it spawns, that
memory is still not paged out.  Memory from the DJGPP image will only be 
paged if the child program needs more DPMI memory than is currently free -
in which case the least recently used pages are paged out (which will 
certainly be the parent image).