Microsoft Windows CE 3.0  


This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

This function notifies NDIS that an Ethernet receive packet, identified in a preceding call to the NdisMEthIndicateReceivefunction, has been fully transferred by the NIC so that NDIS can notify the appropriate bound protocols.

VOID NdisMEthIndicateReceiveComplete(


Handle originally input to the MiniportInitializefunction.


After any Ethernet receive indication, a miniport eventually must call this function to indicate the end of the transfer operation over the net, even if a particular packet is accepted by no bound protocol.

This function both indicates the completion of a transfer operation for a receive and notifies any bound protocol that has already consumed the initial indication that it can begin postprocessing the received data.

When a miniport calls this function, NDIS indicates the completion of the receive operation to each such protocol by calling its ProtocolReceiveCompletefunction.

ProtocolReceiveCompletefunctions need not operate under the severe time constraints of the corresponding ProtocolReceivefunctions. However, another receive indication to the ProtocolReceivefunction can come in while the ProtocolReceiveCompletefunction is running.

A miniport need not call this function in one-to-one correspondence with its calls to the NdisMEthIndicateReceivefunction. That is, an NIC driver can issue a single receive-complete indication for some number of receive indications, particularly when network traffic is high. For example, when a miniport is continually indicating receives from the same source, it might call this function once for every ten indications. On the other hand, a miniport might call this function once for each indication when network traffic is low so that the driver can promptly regain ownership of the memory that it allocated for receives.

A driver that calls this function runs at IRQL DISPATCH_LEVEL.


Runs on Versions Defined in Include Link to
Windows CE OS 2.0 and later Ndis.h    
Note   This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.

See Also


 Last updated on Tuesday, July 13, 2004

© 2004 Microsoft Corporation. All rights reserved.