🚀 go-pugleaf

prunesquallor wrote:
> Dear All,
> 
> I want to lock a page in memory (the reason being it will hold cryptographic 
> keys that I don't want swapped out) - so I don't want to grab much memory.
> 
> Research implies that Windows' VirtualLock will lock the page (such as the 
> MS Documentation). But we've found an early version of the MS document which 
> states that VirtualLock does not lock pages in physical memory, but in the 
> process' working set (it's notable that the modern version of the MS 
> documentation seems to be unclear). It this is the case then should the 
> whole process be slung out to disk then the locked page will go with it.

Quote from the MSDN:

<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.

Eelke