Intel® IXP400 Software

Access-Layer Components: Ethernet Access (IxEthAcc) API

Figure 52. Ethernet Receive Plane Data Buffer Flow

 

Codelet or client application

1. Initializations , Callback

9. Client must free buffers,

Registration...

replenish PortRxFree

 

 

queues

2. PortRxFreeReplenish (Port 0)

 

 

PortRxFreeReplenish (Port 1)

 

 

PortRxFreeReplenish (Port 2)

 

 

 

8.

RxCallback (Port 0)

3. PortEnable (Port 0)

 

RxCallback (Port 1)

 

RxCallback (Port 2)

PortEnable (Port 1)

 

 

 

PortEnable (Port 2)

 

 

 

 

IxEthAcc

4. IxEthAcc will

 

store extra ixp_buf

7. IxEthAcc dispatches

pointers if IxQMgr

port specific callback

port-specific free

functions, passes

queues are full.

ixp_buf pointers

FreeEnet0

FreeEnet1

FreeEnet2

6.IxQMgr dispatches IxEthAcc callback function, passes ixp_buf pointers. If Receive QoS mode, IxEthAcc will place pointers in appropriate Traffic Class queues.

RxEnet

IxQMgr

Optional Priority Queues

5. NPEs receive frames,

Incoming Ethernet Frames

onto RxEnet queue, or

write receive traffic data,

 

muxes ixp_buf pointer

 

multiple RxEnet priority

NPEs

queues, if Receive QoS

mode is enabled.

 

B2366-04

9.5.3.3Additional Receive Path Information

No Receive Polling

An Rx polling interface is not provided for the service. This can easily be extended via queuing the received frames by the access component user and subsequently providing a polling interface.

April 2005

IXP400 Software Version 2.0

Programmer’s Guide

142

Document Number: 252539, Revision: 007

 

Page 142
Image 142
Intel IXP400 manual Additional Receive Path Information, No Receive Polling