NdisCmCloseAddressFamilyComplete - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ndis.h
VOID NdisCmCloseAddressFamilyComplete(
[in] NDIS_STATUS Status,
[in] NDIS_HANDLE NdisAfHandle
);
View the official Windows Driver Kit DDI referenceNo description available.
NdisCmCloseAddressFamilyComplete returns the final status of a client's request, for which the CM's ProtocolCmCloseAf function returned NDIS_STATUS_PENDING, to close the AF.
Status [in]The call manager sets this to NDIS_STATUS_SUCCESS.
NdisAfHandle [in]Specifies the NDIS-supplied handle passed to the call manager's ProtocolCmOpenAf function when this client originally opened the address family.
A stand-alone call manager must call NdisCmCloseAddressFamilyComplete if its ProtocolCmCloseAf function previously returned NDIS_STATUS_PENDING for the given NdisAfHandle . The client, which initiated the pended close-AF operation with a call to NdisClCloseAddressFamily, cannot release the resources it allocated to track communications on the AF until the CM's call to NdisCmCloseAddressFamilyComplete causes a call to that client's ProtocolClCloseAfComplete function.
After a call to NdisCmCloseAddressFamilyComplete, the call manager cannot subsequently use the NdisAfHandle, which becomes invalid for the call manager as soon as this call occurs.
Only stand-alone call managers, which register themselves with NDIS as protocol drivers, can call NdisCmCloseAddressFamilyComplete. Connection-oriented miniport drivers that provide integrated call-management support must call NdisMCmCloseAddressFamilyComplete instead.
NdisMCmCloseAddressFamilyComplete