 Important: |
|---|
| 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 returns pointers to the buffer descriptor and base virtual address for the initial buffer chained to a specified packet descriptor, along with the sizes of the initial buffer and total buffer in case the buffer is fragmented.
VOID NdisGetFirstBufferFromPacket( IN PNDIS_PACKET _Packet , OUT PNDIS_BUFFER * _ FirstBuffer , OUT PVOID * _ FirstBufferVA , OUT PUINT FirstBufferLength , OUT PUINT_ TotalBufferLength );
Parameters
- Packet
- Pointer to the packet descriptor from which this function extracts information about the initial buffer.
- FirstBuffer
- Pointer to a caller-supplied variable in which this function returns the address of the initial buffer descriptor chained to the specified packet descriptor.
- FirstBufferVA
- Pointer to a caller-supplied variable in which this function returns the base virtual address of the initial buffer associated with the packet.
- FirstBufferLength
- Pointer to a caller-supplied variable in which this function returns the number of bytes mapped by the initial buffer descriptor chained to the packet descriptor.
- TotalBufferLength
- Pointer to a caller-supplied variable in which this function
returns the total number of bytes mapped by all buffer descriptors
chained to the packet descriptor.
Remarks
Drivers use this function to get information about the initial buffer and the amount of data associated with a specified packet faster than they can by calling the NdisQueryPacketfunction, and then the NdisQueryBufferfunction.
A driver that calls this function runs at IRQL <= DISPATCH_LEVEL.
Requirements
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
NdisGetNextBuffer, NdisQueryBuffer
Last updated on Tuesday, July 13, 2004