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

More documents

Recommendations

Info

Using Startup Scripts and Configuration Files l l You can modify the system configuration file to run other startup scripts, such as those supplied for the library ACEs. See “Setting Up Particular Configurations” on page 39. You can modify the system configuration file to start user ACEs, either directly (using the ace keyword) or by running the ixsh utility. See “Launching Application ACEs” on page 46. For Additional Information l l l For information on the system and library ACEs, see Chapter 7, “Interface ACEs,” and Chapter 8, “Stack and Library ACEs.” For detailed reference information on the keywords and syntax of the configuration files, see the IXA SDK Reference. Configuration files for sample applications that use various combinations of library ACEs can be found in the following location: SDKinstallpath/src/microace/apps Using Startup Scripts and Configuration Files The IXA SDK provides sample scripts and configuration files that start and configure the interface ACEs and other library ACEs in typical configurations. These files are fully commented. To start a particular configuration of ports and ACEs, including interface ACEs and some set of library and user ACEs, you use the supplied startup scripts, modifying their configuration files for your application and configuration. The basic procedure for starting and exiting the IXA system is as follows: 1. Determine the addresses for your network topology, and modify the system configuration file, ixsys.config, to set up the port configuration 2. Create the necessary configuration files for the library ACEs you are using: — For the L2 bridging ACE, modify l2bridge.config. — For the L3 forwarder ACE, modify l3forwarder.config. — For the NAT ACE, modify nat.config. 3. Add sh commands to the system configuration file, ixsys.config, to run the startup script for each included library ACE, specifying the ACE name and configuration file you have created for each one. 4. After booting the IXDP1200 Advanced Development Platform, run the startup script in the command shell: $ ./ixstart 5. To shut down the modules, run the termination script in the command shell: $ ./ixstop 36 Configuring and Starting IXA Systems Revision 3.3, August 2001
The System Configuration File Starting and Initializing Interface ACEs When you invoke startup script at system boot it does the following: l l l l Activates the specified ports. Sets up and starts the input and output interface ACEs according to the specified configuration. Configures and enables the microengines using Resource Manager calls. Starts threads on the microengines for each port. Microengine Threads The configuration script associates each port to be used with one of the six IXP1200 microengines. The script starts the appropriate threads on each microengine, according to the ports associated with it, so that enough threads are available for each port. l l l Each microengine has four threads. One gigabit port requires eight threads, so it takes two 2 input microblock groups to handle it. One 10/100BaseT port requires one thread, so a microengine can handle up to four such ports. For example, an 8/1 configuration could use two microengines for input on the gigabit port, and two for input on the 8 10/100BaseT ports. This leaves two microengines to handle output for all ports. The System Configuration File The system configuration file specifies the following information for use by the startup script: l l l l l l Which ports to use, and their IP address information. The microcode image to be loaded on each microengine. The configuration for the input and output interface ACEs. Other microACEs to be started, including stack and library ACEs your application will use. Bind configurations for microACEs (both static and dynamic) Shell commands to run. Run the ixsh utility to create, run, and bind conventional ACEs, and run other configuration scripts. The following annotated system configuration file shows how to start and configure the network interfaces and ACEs. This example loads the L3 forwarder library ACE, stack ACE, and input and output ACEs. It sets up binding such that the forwarder receives packets directly from the input ACE and sends them directly to the stack ACE and the output ACE. Revision 3.3, August 2001 Configuring and Starting IXA Systems 37
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 and 26: OMS for Global Application Services
Page 27 and 28: 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: Chapter 4 Configuring and Starting
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 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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?