Re: I/O Queues dispatch methods

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

WDFIOQUEUEs do not use a timer, request presentation is entirely state based. there are 2 axis's of decision

first is queue type, parallel or sequential. if parallel, requests are presented immediately unless the queue is paused. if sequential, one request is presented at a time. when current request is completed, the next request is presented (if there is one).

second is if the queue is power managed or not. if the queue is not power managed, requests are presented based on queue type alone. if it is power managed and the device is idled and powered off, a request will not be presented until the device has power. when the request arrives in the queue, it will trigger power up and be presented later.

there are whitepapers on WHDC (www.microsoft.com/whdc) which describe how to use WDFIOQUEUEs

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"dLopesp" <dLopesp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:EF21A2F3-D638-4DE9-981F-03708BEA0546@xxxxxxxxxxxxxxxx
What triggers a queue causing it to call the registered callbacks if I am
using sequential or parallel dispatching methods? Is it an internal timer or
something like that?
Can someone please describe the internal WDF operation for calling the
queue's callbacks?
Is it possible to configure its behavior and timeout or something?
Thanks in advance.

.

Relevant Pages