Requeuing I/O Requests

Drivers can requeue I/O requests that they obtain from an I/O queue. A driver can requeue a I/O request to another I/O queue that the driver has created for the same device. In addition, a bus driver can requeue an I/O request from a child device's I/O queue to a parent device's I/O queue.

Requeuing an I/O Request to a Different I/O Queue for a Device

After a driver's request handlers receives an I/O request from a driver's I/O queue, the driver can call WdfRequestForwardToIoQueue to requeue the request to another queue.

For example, if you want your driver to allocate resources to a request before processing the request, the driver's EvtIoDefault callback function could receive all requests, store resource information in each request's context memory, and then call WdfRequestForwardToIoQueue to requeue each request to an additional queue.

If your driver calls WdfRequestForwardToIoQueue to requeue an I/O request that the driver obtained from an I/O queue that is using the sequential dispatching method, the framework will deliver the next I/O request from the sequential queue to the driver without waiting for the requeued request to complete.

If your driver is using the manual dispatching method, it can call the WdfRequestRequeue method to return an I/O request to the head of the I/O queue from which the driver obtained it. After calling WdfRequestRequeue, the driver's next call to WdfIoQueueRetrieveNextRequest retrieves the requeued request.

Requeuing an I/O Request to a Parent Device's I/O Queue

A function driver for a parent device can act as a bus driver that enumerates the child devices of the parent device and creates physical device objects (PDOs) for the child devices. Such drivers can sometimes receive I/O requests for a child device that the parent device must handle.

For example, a protocol bus (such as USB) typically controls the hardware resources that are assigned to each connected device. Therefore, the function driver for the parent bus typically handles I/O operations for each child device. When the I/O manager sends an I/O request to the device stack of one of the child devices, the function driver for the bus receives the I/O request in one of the child device's I/O queues, because that driver created the child device's PDO. Before the driver can process the I/O request in the context of the parent bus device, it must requeue the I/O request from the child device's I/O queue to an I/O queue that belongs to the parent device.

However, drivers cannot call WdfRequestForwardToIoQueue to move requests from a child's queue to a parent's queue. Because the I/O manager creates separate device stacks for the parent and child devices, the underlying WDM device object must first be changed from one that represents the child device to one that represents the parent.

Prior to version 1.9 of KMDF, drivers could send I/O requests from a child device to its parent only by creating remote I/O targets, increasing the size of the child device's device stack, and specifying the correct WDM device object.

Beginning with KMDF version 1.9, a driver can call WdfPdoInitAllowForwardingRequestToParent before it creates a child device and then call WdfRequestForwardToParentDeviceIoQueue to requeue a request from the child's I/O queue to a parent queue. If a driver usesWdfPdoInitAllowForwardingRequestToParent and WdfRequestForwardToParentDeviceIoQueue, the framework increases the child's device stack size and assigns the correct WDM device object to the I/O request.

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft