NDIS 6.1 Direct OID Request Interface

NDIS provides a direct OID request interface for NDIS 6.1 and later drivers. The direct OID request path supports OID requests that are queried or set frequently. For example, the IPsec offload version 2 (IPsecv2) interface provides the OID_TCP_TASK_IPSEC_OFFLOAD_V2_ADD_SA OID for direct OID requests. The direct OID request interface is optional for NDIS drivers. To support the direct OID path, drivers provide entry points and NDIS provides NdisXxx functions for protocol, filter, and miniport drivers.

The direct OID request interface is similar to the standard OID request interface. For example, the NdisDirectOidRequest and MiniportDirectOidRequest functions are similar to the NdisOidRequest and MiniportOidRequest functions.

Note  NDIS supports specific OIDs for use with the direct OID request interface. To determine if an OID can be used in the direct OIDs interface, see the OID reference page.

For example, you can use the following OIDs with the direct OID request interface:

Miniport drivers and filter drivers must be able to handle direct OID requests that are not serialized. Unlike the standard OID request interface, NDIS does not serialize direct OID requests with other requests that are sent with the direct OID interface or with the standard OID request interface. Also, miniport drivers and filter drivers must be able to handle direct OID requests at IRQL <= DISPATCH_LEVEL

This section includes:

NDIS Direct OID Request Interface for Connectionless Miniport Drivers

NDIS Direct OID Request Interface for Filter Drivers

NDIS Direct OID Request Interface for Protocol Drivers

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft