Data Fields
EnetUdma_AutoReclaimPrms_s Struct Reference

CPSW channel/flow auto-reclaim config struct. More...

#include <enet_udma.h>

Data Fields

bool enableFlag
 
EnetUdma_DmaDescQHandle hDmaDescPool
 
Udma_RingHandle hReclaimRing
 

Detailed Description

CPSW channel/flow auto-reclaim config struct.

Field Documentation

bool EnetUdma_AutoReclaimPrms_s::enableFlag

Auto-reclaim enable flag Auto-reclaim or auto-recycling of buffer descriptors enables usage of same buffer descriptor between RX flow and TX channel. For example - by using auto-reclaim of RX FQ as TX CQ, we don't need to call EnetUdma_retrieveTxDonePackets and EnetUdma_submitRxReadyPackets in packet forwarding use-cases like SW interVLAN routing Note that current design offers/provides way to use TX FQ as RX CQ but not vice versa (RX CQ as TX FQ), similarly for RX FQ as TX CQ case. This is done due to UDMA HW design where FQ ring number is same as channel number. Basically any ring can't be attached as FQ ring to TX channel. Though this limitation doesn't exist for RX flow, we keep design consistent and enable auto-reclaim of RX FQ as TX CQ

EnetUdma_DmaDescQHandle EnetUdma_AutoReclaimPrms_s::hDmaDescPool

Handle to free DMA descriptor pool where a free descriptors retrieved in EnetUdma_retrieveRxPackets() function. This is as we bypass EnetUdma_retrieveTxDonePackets() in auto-reclaim

Udma_RingHandle EnetUdma_AutoReclaimPrms_s::hReclaimRing

handle to ring used in auto-reclaim. For example when using TX CQ –> RX FQ, the RX FQ ring handle is passed by an app to be used as TX CQ so default ring should not be allocated/used


The documentation for this struct was generated from the following file:

Copyright 2020, Texas Instruments Incorporated