Process Explorer and locked bytes?

NTFSD
1

Is there any way in Process Explorer (or another utility) to tell how much
virtual memory a process has locked? I’ve looked through it, but it does
not appear to be there. Would be a great enhancement, though.

2

Not exactly sure what info you’re looking for, but have you tried VMMap?
Shows a pretty interesting overview of the address space of a process, maybe
you can find what you’re looking for there.

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Neil Weicher” wrote in message news:xxxxx@ntfsd…
> Is there any way in Process Explorer (or another utility) to tell how much
> virtual memory a process has locked? I’ve looked through it, but it does
> not appear to be there. Would be a great enhancement, though.
>
>

3

> Is there any way in Process Explorer (or another utility) to tell how much

virtual memory a process has locked? I’ve looked through it, but it does
not appear to be there. Would be a great enhancement, though.

Locked as in VirtualLock, or MmProbeAndLockPages?

!process xxx 1 in kd will show the latter, and !wsle can be used to
estimate the former (the FirstDynamic value it reports is the index
of the first non-locked working set entry. It’s not exactly the number
of VirtualLock’ed pages because a small number of Mm internal
entries are always reported as locked).

The VirtualLock locked bit is exposed through the QueryWorkingSetEx
API, so there might be some user mode tools that show it.

–
Pavel Lebedinsky/Windows Fundamentals Test
This posting is provided “AS IS” with no warranties, and confers no rights.

4

“Pavel Lebedinsky” wrote in message
news:xxxxx@ntfsd…
>> Is there any way in Process Explorer (or another utility) to tell how
>> much virtual memory a process has locked? I’ve looked through it, but it
>> does not appear to be there. Would be a great enhancement, though.
>
> Locked as in VirtualLock, or MmProbeAndLockPages?
>
> !process xxx 1 in kd will show the latter, and !wsle can be used to
> estimate the former (the FirstDynamic value it reports is the index
> of the first non-locked working set entry. It’s not exactly the number
> of VirtualLock’ed pages because a small number of Mm internal
> entries are always reported as locked).
>
> The VirtualLock locked bit is exposed through the QueryWorkingSetEx
> API, so there might be some user mode tools that show it.
>

Sorr I wasn’t clear. I’m talking about user address space as in VirtualLock.

5

“Scott Noone” wrote in message news:xxxxx@ntfsd…
> Not exactly sure what info you’re looking for, but have you tried VMMap?
> Shows a pretty interesting overview of the address space of a process,
> maybe you can find what you’re looking for there.
>
> -scott
>

Looks like VMMap is what I was looking for. Thanks!