Yes, our underlying implementation uses ExQueueWorkItem with you
specifying the type of queue to use.
Dan, for what you are doing I think you should manage your own threads.
The idea of having the filter manager provide low priority worker
threads is a good one. I have filed an enhancement request to do this.
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 Dan Kyler
Sent: Friday, March 04, 2005 9:07 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Filter manager generic work threads and long
operations
executive work queues run at a high
>priority (13+) that I find seldom provides the "low priority
background
Yuck. This is exactly the kind of task I want to run at a low
priority. Couldn’t one set the priority of the thread for the duration
of
the work item? It wouldn’t prevent the immediate preemption, but it
would
allow a long task to be friendlier to the system.
Thanks,
"At 11:36 AM 3/4/2005 -0500, Tony wrote:
I’m not sure whether they use ex queues or not (Neal? Molly?), but if
they do I’d recommend using your own queues in order to avoid the
deadlocks we see periodically when using ex queues in a file system
filter driver.
Another advantage of using your own work queues is that it allows you
to
control the scheduling policy - executive work queues run at a high
priority (13+) that I find seldom provides the “low priority
background”
model for asynchronous operations. In fact, if the priority of the
current thread is below this, what normally happens is that this causes
an immediate pre-emption and the worker thread starts running - which
is
seldom what I want when posting to a work thread.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Dan Kyler
Sent: Friday, March 04, 2005 11:27 AM
To: ntfsd redirect
Subject: [ntfsd] Filter manager generic work threads and long
operations
In a minifilter, for an operation that may take a long time (on the
order
of hours), and could potentially have many copies running at the same
time,
is it acceptable to use FltQueueGenericWorkItem, or should I manage my
own
pool of threads for this?
I am assuming (dangerous, I know) that FltQueueGenericWorkItem uses Ex
worker threads, in which case I think this scenario would be a bad
thing. With my own pool of threads, I can better control the
simultaneous
number of these work items and not clog up the Ex worker thread pool
with
long term work.
Opinions anyone?
Thanks,
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
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