Intel IXA SDK ACE Programming Framework - Department of ...

More documents

Recommendations

Info

OMS for Global Application Services Network interface ACE Target T1 Packet flow ACE 1 Decision? Target T2 Target T3 ACE 2 Processing Target T4 The management program for an application binds and unbinds targets and ACEs using Resolver functions (ix_res_bind and ix_res_unbind) that are part of the OMS services. The IXA SDK also supplies utilities to bind ACEs and targets from the command line or from a script. The target mechanism makes the actual identities of the ACEs transparent to the action code that forwards the packets. The management part of your application can change the bindings of targets to ACEs to alter the path of packet flow, without you having to change the code in the ACEs themselves. For more information, see Chapter 5, “Controlling Packet Flow.” Communicatio n Among ACEs ACEs often need to communicate with one another or with a managing application for various reasons. For example: l l l ACEs can send alerts or status reports to the managing application. ACEs in a data processor module can receive control messages and data from ACEs in a control module. ACEs can send occasional packet data to other ACEs for special processing, or can exchange messages among themselves to coordinate packet processing. Because ACEs and their managing application might be running on different platforms and be written in different languages, the OMS acts as a message broker, using a remote procedure call model for object communication. ACEs and tasks communicate using a crosscall interface for remote method invocation. Remote method calls are handled through the distributed OMS, which provides marshalling and format conversion to address differences in byte order and word size between different processors. An ACE or task can act as a server or a client for remote procedure calls. l l The call server contains a crosscall object with the call method implementation. The call client makes remote calls to the call server using a crosscall reference object. 12 Introduction and Overview Revision 3.3, August 2001
OMS for Global Application Services rules actions Remote procedure call CAP, crosscall reference OMS Communication Controller Client ACE Packet flow Packet classification CAP, crosscall Response (optional) Related actions Server ACE You define a crosscall interface for an application using an interface definition language, IXA IDL, that is provided with the IXA SDK. IXA IDL is not OMG IDL; it has been refined to specifically target the type of interfaces needed in network packet processing applications, rather than interfaces for general purpose applications. You define calls to be synchronous or asynchronous, with or without a response. The definition compiles to C code that implements the crosscall infrastructure, which you then modify to provide specific call functions. l l Modify the crosscall source file to implement application-specific call functions. Compile the source code into the call server executable. For asynchronous calls with response (deferred calls), modify the callback source file to implement the callback function that is executed when the call completes. Compile the source code for the crosscall references (stubs) and callbacks into the call client executable. Library ACEs and system ACEs typically export crosscall interfaces. ACEs defined in your application must import these interfaces and include the crosscall references in order to invoke the calls in the predefined ACEs. MicroACE Resource Manager Programs running on the core processor, including the core components of micro- ACEs and ACE management applications, communicate with the microengines using the microACE Resource Manager. The Resource Manager is system software that runs in the core processor kernel. The Resource Manager API allows a microACE management program to do the following: l l l l l Initialize and configure the IXP1200. Load code onto microengines. Enable and disable the microengines. Get and set the microengine configuration and resource assignments. Allocate and access uncached SRAM, SDRAM and scratch memory. Introduction and Overview 13 Revision 3.3, August 2001
Page 1 and 2: Intel ® IXA SDK ACE Programming Fr
Page 3 and 4: Contents About This Guide. . . . .
Page 5 and 6: L2 Bridging Configuration File . .
Page 7 and 8: ICMP Error Packet Handling . . . .
Page 9 and 10: About This Guide This guide introdu
Page 11 and 12: Other Sources of Information Other
Page 13 and 14: Contacting Intel http://support.int
Page 15 and 16: Chapter 1 Introduction and Overview
Page 17 and 18: Logical Elements of an IXA Applicat
Page 19 and 20: The ACE Programming Framework for P
Page 25: OMS for Global Application Services
Page 29 and 30: Hardware Architecture: The IXP1200
Page 31 and 32: Components of the IXA SDK for the I
Page 33 and 34: Chapter 2 Elements of an Applicatio
Page 35 and 36: The Object Management System l The
Page 37 and 38: ACEs and Support Structures To crea
Page 39 and 40: The Application Building Process Th
Page 41 and 42: The Application Building Process c.
Page 43 and 44: Chapter 3 Compiling and Testing App
Page 45 and 46: Overview of the ACE Compilation and
Page 47 and 48: Using Makefiles l The microengine t
Page 49 and 50: Chapter 4 Configuring and Starting
Page 51 and 52: The System Configuration File Start
Page 53 and 54: Setting Up Particular Configuration
Page 61 and 62: Chapter 5 Controlling Packet Flow T
Page 63 and 64: Binding Targets as Packet Destinati
Page 65 and 66: Directing Packets to a Target //all
Page 67 and 68: Receiving and Transmitting on Netwo
Page 69 and 70: Chapter 6 Writing MicroACEs This ch
Page 71 and 72: MicroACE Architectural Elements Arc
Page 73 and 74: Loading MicroACEs 8. Start the micr
Page 75 and 76: Writing the Core Component of a Mic
Page 77 and 78:
Writing the Core Component of a Mic
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Microblock Types and Groups You wri
Page 85 and 86:
Writing a Dispatch Loop Block Type
Page 87 and 88:
Writing a Dispatch Loop Defining Ad
Page 89 and 90:
Writing a Microblock DL_SASink#: DL
Page 91 and 92:
MicroACE Design Example .elif (dl_n
Page 93 and 94:
Chapter 7 Interface ACEs This chapt
Page 95 and 96:
Initializing Interface ACEs A compl
Page 97 and 98:
The Input ACE The Input ACE The inp
Page 99 and 100:
The Output ACE l l l l l l Initiali
Page 101 and 102:
Chapter 8 Stack and Library ACEs Th
Page 103 and 104:
The L3 Forwarder Library ACE You ca
Page 105 and 106:
The L2 Bridging Library ACE The L3
Page 107 and 108:
The L2 Bridging Library ACE Conditi
Page 109 and 110:
The NAT Library ACEs — IP masquer
Page 111 and 112:
The NAT Library ACEs ace natc ./nat
Page 113 and 114:
Chapter 9 Classifying Packets Using
Page 115 and 116:
Defining Rules as “the set of all
Page 117 and 118:
How Rules Are Evaluated protocol et
Page 119 and 120:
Chapter 10 Initializing and Acting
Page 121 and 122:
Initializing the ACE Your ACE also
Page 123 and 124:
Defining Action and Utility Functio
Page 125 and 126:
What Action Functions Do Table 1: (
Page 127 and 128:
Chapter 11 Communication Within an
Page 129 and 130:
Overview Each call client or server
Page 131 and 132:
Defining Crosscall Interfaces Use t
Page 133 and 134:
Defining Call Operations Operation
Page 135 and 136:
Invocation Types for Operations l l
Page 137 and 138:
Integrating Crosscalls with Applica
Page 139 and 140:
Initializing and Terminating Interf
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Invoking Crosscall Functions ix_err
Page 147 and 148:
Passing Crosscall Arguments } sleep
Page 149 and 150:
Passing Crosscall Arguments — For
Page 151 and 152:
Passing Crosscall Arguments 3. Call
Page 153 and 154:
Chapter 12 Crosscall Example This c
Page 155 and 156:
Example Interface Definition /* Dec
Page 157 and 158:
Example Interface Definition /*****
Page 159 and 160:
Writing the Crosscall Client static
Page 161 and 162:
Writing the Crosscall Client } goto
Page 163 and 164:
Writing the Crosscall Client err =
Page 165 and 166:
Writing the Crosscall Client err_la
Page 167 and 168:
Writing the Crosscall Server This e
Page 169 and 170:
Writing the Crosscall Server } if(r
Page 171 and 172:
Writing the Crosscall Server } /***
Page 173 and 174:
Writing the Crosscall Server // ACE
Page 175 and 176:
Chapter 13 Using Sets of Data to Cl
Page 177 and 178:
Defining Sets and Searches You can
Page 179 and 180:
Initializing and Populating Sets ix
Page 181 and 182:
How to Use Sets and Searches err =
Page 183 and 184:
Index A ACE 5 accelerated 7 action
Page 185 and 186:
D data processing plane 3 data sets
Page 187 and 188:
NAT library ACEs 94 binding targets
Page 189 and 190:
full names of 21 L3 forwarder ACE 9
Page 191 and 192:
Revision 3.3, August 2001 177
show all

Intel IXA SDK ACE Programming Framework - Department of ...

Create successful ePaper yourself

Delete template?

Save as template?