🚀 go-pugleaf

"Eelke" wrote:

>

> <quote>

> The working set of a process is the set of memory pages currently

> visible to the process in physical RAM memory. These pages are

> resident and available for an application to use without triggering a page 
> fault.

> The minimum and maximum working set sizes affect the virtual memory

> paging behavior of a process.

> </quote>

>

> So I would conclude that locking into the working set is the same as

> locking into physical RAM.

>

Unfortunately, I don't think it's quite that simple. That was my original 
conclusion until I found another quote on MSDN:

"Processes in Windows NT are granted subtle influence into this system 
behavior with the VirtualLock and VirtualUnlock functions. Essentially, a 
process can establish specific pages to lock into its working set. However, 
this does not give the process free reign over its working set. It cannot 
affect the number of pages that make up its working set (the system adjusts 
the working set for each process routinely), and it cannot control when the 
working set is in memory and when it is not."

That's saying that the whole lot can be shoved to disk under certain 
conditions.

That's why we're currently not convinced that VirtualLock does truly lock 
pages into physical memory.

TTFN

JB