1. EXU lock_memory ??
EXU has no lock_memory.
I know that linux uses a swap file.
What happens if you allocate memory and want it to keep it
from being swapped out ?
I also assume that there is no extender so I don't know what
the answer is.
Thanks Bernie
2. Re: EXU lock_memory ??
- Posted by Robert Craig <rds at ATTCANADA.NET>
Aug 29, 2000
-
Last edited Aug 30, 2000
Bernie Ryan writes:
> EXU has no lock_memory.
> I know that linux uses a swap file.
> What happens if you allocate memory and want it to keep it
> from being swapped out ?
On DOS you *need* lock_memory() to prevent
hardware interrupt handling code from being
swapped out by CauseWay. A crash can result if your
interrupt-handling code is swapped out.
Linux is a much more sophisticated O/S than DOS
(to say the least!). On Linux you would write a device driver
to handle device interrupts. Writing device drivers is not
for the faint of heart.
There may be a way to lock a process in memory with Linux,
but you rarely need to worry about that. The O/S will keep your
process in memory if it is being actively used.
> I also assume that there is no extender so I don't know what
> the answer is.
No extender is needed on Linux.
DOS needs an extender to get around the 640K barrier.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
