Mail Archives: djgpp/1997/04/01/04:16:42
On Mon, 31 Mar 1997, Edward Schlunder wrote:
> Why can't you just say that everything in one object file is dangerous
> and shouldn't be paged out?
Who said you can't? Just call the locking functions with appropriate
arguments, and that object file will be locked. If you somehow find
the way you should call those locking functions inconvenient, please
tell why, and how would you like them to become more convenient.
> Also, in my program, I -know- I don't have some parts of the interrupt
> handler code and data locked, yet I never get page fault errors. How do
> I force a page fault if it is possible to happen?
Use any of the available ways to eat up some of the physical memory
before you run your program. If you don't have any such tools handy,
you can write a trivial 2-liner that `calloc's a chunk of RAM, then
spawns your program. You can play with the amount of `calloc'ed
memory to make sure your program pages. Note that you need to call
`calloc', not `malloc', because some DPMI hosts won't page in memory
unless it's actually accessed.
- Raw text -