Hi,
My filesystem filter driver shows that process which flushes buffers
from cache runs with PsGetCurrentProcessId()=4. Can I assume that it
has ProcID==4 always on all OSes starting from Win2k? If not, is there
a way to get know what ProcID does Cache Manager have?
If I intercept an IRP in the context of Cache Manager does it mean
that the dispatch routine is running in nonarbitrary thread context,
i.e. can I use KeWaitForSingleObject in it?
–
Roman Kudinov
What you are describing is the process ID of the system process. There
are lots of threads which run in this process including worker threads
which is what the lazy writer uses.
Note that the process ID of the system process has changed among various
OS releases.
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no
rights
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roman Kudinov
Sent: Saturday, August 28, 2004 3:01 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Cache Manager
Hi,
My filesystem filter driver shows that process which flushes buffers
from cache runs with PsGetCurrentProcessId()=4. Can I assume that it
has ProcID==4 always on all OSes starting from Win2k? If not, is there
a way to get know what ProcID does Cache Manager have?
If I intercept an IRP in the context of Cache Manager does it mean
that the dispatch routine is running in nonarbitrary thread context,
i.e. can I use KeWaitForSingleObject in it?
–
Roman Kudinov
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
> from cache runs with PsGetCurrentProcessId()=4. Can I assume that it
has ProcID==4 always on all OSes starting from Win2k? If not, is there
a way to get know what ProcID does Cache Manager have?
Why do you need this?
If I intercept an IRP in the context of Cache Manager does it mean
that the dispatch routine is running in nonarbitrary thread context,
i.e. can I use KeWaitForSingleObject in it?
You cannot block the paging writes.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com