NdisDirectOidRequest function

The NdisDirectOidRequest function forwards a direct OID request to the underlying drivers to query the capabilities or status of an adapter or set the state of an adapter.

Syntax


NDIS_STATUS NdisDirectOidRequest(
  _In_  NDIS_HANDLE NdisBindingHandle,
  _In_  PNDIS_OID_REQUEST OidRequest
);

Parameters

NdisBindingHandle [in]

The handle that the NdisOpenAdapterEx function returns that identifies the target miniport adapter on the binding.

OidRequest [in]

A pointer to an NDIS_OID_REQUEST structure that specifies the operation that is requested with a given OID_Xxx code to either query the status of an adapter or to set the state of an adapter.

Return value

The underlying driver determines which NDIS_STATUS_XXX code NdisDirectOidRequest returns, but it is usually one of the following values:

Return codeDescription
NDIS_STATUS_SUCCESS

The request operation completed successfully.

NDIS_STATUS_PENDING

The request is being handled asynchronously, and NDIS will call the caller's ProtocolDirectOidRequestComplete function when the request is completed.

NDIS_STATUS_INVALID_OID

The OID_Xxx code that was specified in the Oid member of the NDIS_OID_REQUEST-structured buffer at OidRequest was invalid or unsupported by the underlying driver.

NDIS_STATUS_INVALID_LENGTH or NDIS_STATUS_BUFFER_TOO_SHORT

The value that was specified in the InformationBufferLength member of the NDIS_OID_REQUEST-structured buffer at OidRequest did not match the requirements for the given OID_Xxx code. If the information buffer was too small, the BytesNeeded member contains the correct value for InformationBufferLength on return from NdisDirectOidRequest.

NDIS_STATUS_INVALID_DATA

The data that was supplied at InformationBuffer in the given NDIS_OID_REQUEST structure was invalid for the given OID_Xxx code.

NDIS_STATUS_NOT_SUPPORTED or NDIS_STATUS_NOT_RECOGNIZED

The underlying driver does not support the requested operation. For NdisDirectOidRequest, NDIS can also return this status if the calling driver has not registered a ProtocolDirectOidRequestComplete function.

NDIS_STATUS_RESOURCES

The request could not be satisfied because of a resource shortage. Typically, this return value indicates that an attempt to allocate memory was unsuccessful, but it does not necessarily indicate that the same request, submitted later, will be failed for the same reason.

NDIS_STATUS_NOT_ACCEPTED

The underlying driver attempted the requested operation, typically a set on a NIC, but it failed. For example, an attempt to set too many multicast addresses might cause the return of this value.

NDIS_STATUS_CLOSING or NDIS_STATUS_CLOSING_INDICATING

The underlying driver failed the requested operation because a close operation is in progress.

NDIS_STATUS_RESET_IN_PROGRESS

The underlying miniport driver cannot satisfy the request at this time because it is currently resetting the affected NIC. The caller's ProtocolStatusEx function was or will be called with NDIS_STATUS_RESET_START to indicate that a reset is in progress. This return value does not necessarily indicate that the same request, submitted later, will be failed for the same reason.

NDIS_STATUS_FAILURE

This value typically is a non-specific default, returned when none of the more specific NDIS_STATUS_Xxx values caused the underlying driver to fail the request.

 

Remarks

The NdisDirectOidRequest function cannot be used for general OID requests. For general OID requests, use the NdisOidRequest function instead. NdisDirectOidRequest can be used only for OIDs that NDIS supports for use with the direct OID interface. For example, the following OIDs can be used:

OID_TCP_TASK_IPSEC_OFFLOAD_V2_ADD_SA

OID_TCP_TASK_IPSEC_OFFLOAD_V2_DELETE_SA

OID_TCP_TASK_IPSEC_OFFLOAD_V2_UPDATE_SA

A protocol driver must allocate sufficient memory to hold the information buffer that is associated with the specified OID. The driver must also allocate and set up the buffer at the OidRequest parameter before it calls NdisDirectOidRequest. Both buffers must be allocated from nonpaged pool because the underlying driver runs at raised IRQL while processing the request.

NdisDirectOidRequest forwards a request to underlying drivers or handles the request itself. If the next-lower driver is an NDIS intermediate driver, the intermediate driver can call NdisDirectOidRequest with an OID-specific request of its own before completing the request that the higher-level driver originally submitted.

A driver that calls NdisDirectOidRequest must register the ProtocolDirectOidRequestComplete function.

The direct OID request interface is similar to the general OID request interface. For more information about issuing general requests, see NdisOidRequest.

Note  Although Direct OID requests are not generally serialized, NDIS itself may still pend a request with NDIS_STATUS_PENDING and queue the request for later completion. For example, NDIS may pend and queue a Direct OID request sent to a selective suspend miniport that is currently in a low power state. Protocols and filters must be prepared to handle an NDIS_STATUS_PENDING code, even if the underlying miniport would complete the request synchronously.

Requirements

Version

Supported in NDIS 6.1 and later.

Header

Ndis.h (include Ndis.h)

IRQL

<= DISPATCH_LEVEL

See also

NDIS_OID_REQUEST
OID_TCP_TASK_IPSEC_OFFLOAD_V2_ADD_SA
OID_TCP_TASK_IPSEC_OFFLOAD_V2_DELETE_SA
OID_TCP_TASK_IPSEC_OFFLOAD_V2_UPDATE_SA
NdisOidRequest
NdisOpenAdapterEx
ProtocolDirectOidRequestComplete
ProtocolStatusEx

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft