Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Storage Filter Drivers

This section contains the following information:

Storage Filter Driver's Support of I/O Requests

Storage Filter Driver's Device-Type-Specific Functionality

Storage Filter Driver's DriverEntry Routine

Storage Filter Driver's AddDevice Routine

Handling PnP Start in a Storage Filter Driver

Storage Filter Driver's Dispatch Routines

Storage Filter Driver's IoCompletion Routines

Handling PnP Paging Requests

If a storage class driver already exists for a particular type of device, it might be unnecessary to write a driver for a new device of the same type. Each system-supplied storage class driver is designed to support peripheral devices of a given type and is tested against a number of vendors' devices. Thus, any system-supplied storage class driver might provide all the support another device of its type needs.

If an existing storage class driver does not fully support a new device of its type, a new driver can be written as a storage filter driver (SFD) layered over or under an existing system-supplied class driver. An SFD might transform data in read/write requests, define additional I/O control codes (IOCTLs) that enable a user application to take advantage of additional features of a particular device, or work around device-specific problems without requiring hardware-specific changes to the generic class or port drivers.

Unless a new device requires that every request be handled in a device-specific manner, a storage filter driver can be developed in far less time than a new storage class driver.

 

 

Send comments about this topic to Microsoft

Show:
© 2015 Microsoft