BOOLEAN
MiniportCheckForHang(
IN NDIS_HANDLE MiniportAdapterContext
);
MiniportCheckForHang is an optional function that reports the state of the NIC or monitors the responsiveness of an underlying device driver.
Parameters
MiniportAdapterContext
Specifies the handle to a miniport-allocated context area in which the driver maintains per-NIC state, set up by MiniportInitialize.
Return Value
MiniportCheckForHang returns TRUE if the driver determines that its NIC is not operating or if an intermediate driver determines that the underlying device driver is unresponsive.
Comments
In NIC drivers, MiniportCheckForHang does nothing more than check the internal state of the NIC and return TRUE if it detects that the NIC is not operating correctly.
In intermediate drivers, MiniportCheckForHang can periodically check the state of the driver’s virtual NIC to determine whether the underlying device driver appears to be hung.
By default, the NDIS library calls MiniportCheckForHang approximately every two seconds.
If MiniportCheckForHang returns TRUE, NDIS then calls the driver’s MiniportReset function.
If a NIC driver has no MiniportCheckForHang function and NDIS judges the driver unresponsive as, for example, when NDIS holds many pending sends and requests queued to the miniport for a time-out interval, NDIS calls the driver’s MiniportReset function. The NDIS library’s default time-out interval for queued sends and requests is around four seconds. However, a NIC driver’s MiniportInitialize function can extend NDIS’s time-out interval by calling NdisMSetAttributesEx from MiniportInitialize to avoid unnecessary resets.
The MiniportInitialize function of an intermediate driver should disable NDIS’s time-out interval with NdisMSetAttributesEx because such a driver can neither control nor estimate a reasonable completion interval for the underlying device driver.
MiniportCheckForHang can be pre-empted by an interrupt.
By default, MiniportCheckForHang runs at IRQL DISPATCH_LEVEL.
See Also