Date: Fri, 7 Feb 1997 12:38:43 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "K.A.R.L." <farega AT usc DOT es>
cc: djgpp AT delorie DOT com
Subject: Re: OpenDOS and DJGPP
In-Reply-To: <32F9F2D0.3890@usc.es>
Message-ID: <Pine.SUN.3.91.970207123029.7639B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Thu, 6 Feb 1997, K.A.R.L. wrote:

>         DPMI memory available: 4479 Kb
>         DPMI swap space available: 10585 Kb

These numbers seem OK (although the swap space seems a bit low).

> 	LH NWCACHE 2048 1024 /LEND=ON /DELAY=OFF
                                       ^^^^^^^^^
Does this mean that the cache is write-through (i.e. only caches reads, 
but not writes)?  If so, and if your MSDOS configuration used a 
write-back cache, then this might be the reason.  Are you sure that what 
you see is that GCC pages to disk?  Maybe these are the temporary files 
that the compiler passes use?  Please read section 7.1 of the DJGPP FAQ 
list for explanation of how to see whether GCC runs out of physical 
memory.

If it appears that the disk traffic which you see is indeed due to
temporary files and not to virtual memory paging, you should consider
changing your disk cache configuration to make it write-back (don't know
how to do that with NWCACHE, but the FAQ explains how this is done with 
SmartDrv). 

In any case, I suggest trying to run with the same disk cache as your 
MSDOS configuration does, and see if that makes any difference.