MiniportTransferData (Compact 2013)

Article
07/31/2017

3/26/2014

This function is required for network adapter drivers that do not indicate multipacket receives and media-specific information with NdisMIndicateReceivePacket and in those that do not support WAN media.

Syntax

NDIS_STATUS MiniportTransferData(
  PNDIS_PACKET Packet,
  PUINT BytesTransferred,
  NDIS_HANDLE MiniportAdapterContext,
  NDIS_HANDLE MiniportReceiveContext,
  UINT ByteOffset,
  UINT BytesToTransfer
);

Parameters

Packet
[out] Points to a packet descriptor with chained buffers into which MiniportTransferData should copy the received data.

BytesTransferred
[out] Points to a variable that MiniportTransferData sets to the number of bytes it copied into the packet. This value is meaningless if MiniportTransferData returns NDIS_STATUS_PENDING.

MiniportAdapterContext
[in] Specifies the handle to a miniport-allocated context area in which the driver maintains per-network adapter state, set up by MiniportInitialize.

MiniportReceiveContext
[in] Specifies the context handle previously passed to NdisMXXXIndicateReceive. The miniport can examine this value to determine which receive to copy.

ByteOffset
[in] Specifies the offset within the received packet at which MiniportTransferData should begin the copy. If the whole packet is be copied, ByteOffset is zero.

BytesToTransfer
[in] Specifies how many bytes to copy. The sum of ByteOffset and BytesToTransfer should be less than or equal to the packet size that was specified in the miniport's receive indication. This value can be zero.

Return Value

Value	Description
NDIS_STATUS_SUCCESS	MiniportTransferData copied the requested data into the protocol-supplied packet, and it set BytesTransferred to the number of bytes copied.
NDIS_STATUS_PENDING	The driver will complete the transfer asynchronously with a call to NdisMTransferDataComplete.
NDIS_STATUS_FAILURE	Either the data could not be copied or the input transfer range was invalid.

Remarks

MiniportTransferData copies the contents of the received packet to a given protocol-allocated packet.

NDIS calls MiniportTransferData when a ProtocolReceive function calls NdisTransferData. The media header associated with a packet cannot be copied; only the data section of a packet can be copied. The range passed to NdisTransferData never includes the media header. Usually, the ByteOffset input to MiniportTransferData excludes data that the miniport already indicated in the lookahead buffer.

A miniport must be prepared to copy a given packet multiple times. If its network adapter supports reading a given packet only one time, the miniport must copy each received network packet to a staging buffer.

MiniportTransferData can call NdisQueryPacket to determine how many buffer descriptors the allocating protocol has provided. The protocol is responsible for supplying a packet descriptor that accommodates the transfer it requested. MiniportTransferData can call NdisQueryBuffer to determine how much data to copy to each protocol-supplied buffer.

MiniportTransferData can fail a request if the given ByteOffset and BytesToTransfer exceed the packet size originally indicated. Or, MiniportTransferData can transfer all available data starting at any valid ByteOffset.

Because MiniportTransferData is asynchronous, a miniport that has this function cannot deliver receive indications while a transfer is pending. If MiniportTransferData returns NDIS_STATUS_PENDING, the miniport must call NdisMTransferDataComplete when the transfer is complete.

A driver that indicates packets with NdisMIndicateReceivePacket does not have to have a MiniportTransferData function because such a driver always indicates full packets to bound protocols.

Interrupts are still disabled when MiniportTransferData is called.

Requirements

Header

externs.h

Partager via

MiniportTransferData (Compact 2013)

Syntax

Parameters

Return Value

Remarks

Requirements

See Also

Reference

Ressources supplémentaires