NdisAllocatePacketPoolEx (Windows Embedded CE 6.0)

1/6/2010

This function allocates and initializes a block of storage for a pool of packet descriptors.

Syntax

VOID NdisAllocatePacketPoolEx(
  PNDIS_STATUS Status,
  PNDIS_HANDLE PoolHandle,
  UINT NumberOfDescriptors,
  UINT NumberOfOverflowDescriptors,
  UINT ProtocolReservedLength
);

Parameters

• Status
  [out] Points to a caller-supplied variable in which this function returns the status of the packet pool allocation.

• PoolHandle
  [out] Points to a caller-supplied variable in which this function returns a handle to the packet pool. This handle is a required parameter to the NdisXXXPacket functions that the driver calls subsequently.

• NumberOfDescriptors
  [in] Specifies the number of packet descriptors that the pool should contain for anticipated normal use. The maximum NumberOfDescriptors that can be allocated is 0xFFFF. If an attempt is made to allocate more than this, NdisAllocatePacketPoolEx returns a Status of NDIS_STATUS_RESOURCES.

• NumberOfOverflowDescriptors
  [in] Specifies the number of packet descriptors reserved for an overflow situation, that is, when all the descriptors specified by NumberOfDescriptors are in use. If the sum of this parameter and NumberOfDescriptors exceeds 0xFFFF, NdisAllocatePacketPoolEx reduces the value supplied as this parameter so that the total NumberOfDescriptors and NumberOfOverflowDescriptors equals 0xFFFF.

• ProtocolReservedLength
  [in] Specifies the number of bytes to be allocated for the ProtocolReserved array of each packet descriptor. For packet descriptors to be used in receive indications, this parameter is 4*size of (PVOID).

Return Value

The following table shows the possible return values for this function.

Remarks

A successful call to NdisAllocatePacketPoolEx returns a handle to the packet pool, which the caller should save. Usually, the driver next calls NdisAllocatePacket one or more times with this handle to allocate a set of packet descriptors.

NdisAllocatePacketPoolEx statically allocates only enough memory to accommodate the number of packet descriptors specified by NumberOfDescriptors. The total number of packet descriptors that can be allocated from the pool with calls to NdisAllocatePacket is the lesser of 0xFFFF or the sum of NumberOfDescriptors and NumberOfOverflowDescriptors originally passed to NdisAllocatePacketPoolEx. Overflow descriptors are allocated dynamically only during an overflow situation — that is, when the given NumberOfDescriptors have already been allocated and are still in use.

The sum of NumberOfDescriptors and NumberOfOverflowDescriptors is the effective limit on how many times the driver can call NdisAllocatePacket before it must call NdisFreePacket to return a packet descriptor to the free list for the packet pool. When no overflow descriptor has yet been allocated, NdisFreePacket returns the packet descriptor to the statically allocated pool. If one or more overflow descriptors have already been allocated, NdisFreePacket returns the packet descriptor to system memory — not to the pool.

The caller of NdisAllocatePacketPoolEx should set NumberOfDescriptors to the number of packet descriptors needed for anticipated normal loads. The driver should set NumberOfOverflowDescriptors to the number of additional descriptors needed to accommodate anticipated peak loads. If the total possible number of packet descriptors (NumberOfDescriptors plus NumberOfOverflowDescriptors) has been allocated from the pool, a call to NdisAllocatePacket returns NDIS_STATUS_RESOURCES.

As packets sent or indicated are returned to the allocating driver, it can reuse each packet descriptor after calling NdisReinitializePacket and setting it up again with a chain of buffer descriptors, or the driver can call NdisFreePacket to return that packet to the free list. Reinitializing and reusing packets allocated from packet pool is far faster than freeing and, then, having to reallocate them again. Before a driver calls NdisReinitializePacket with a packet descriptor, it must save the pointers to buffer descriptors that are chained to the packet descriptor, because NdisReinitializePacket sets the head of the buffer chain to NULL.

When a driver no longer needs packet descriptors, it calls NdisFreePacketPool to release the storage that it allocated with NdisAllocatePacketPoolEx.

Requirements

See Also

Reference

NDIS Library Functions
NdisAllocatePacket
NdisDprAllocatePacket
NdisDprAllocatePacketNonInterlocked
NdisFreePacketPool
NdisMIndicateReceivePacket
NDIS_PACKET
NDIS_PACKET_OOB_DATA
NdisReinitializePacket
NdisSendPackets
NdisUnchainBufferAtBack
NdisUnchainBufferAtFront