Ubiquitous Component Remoting Support on Overlay Network Adaptation support with Ontology-based annotation Roaming support of wireless component communication Switching support of component communication using network processors Streaming support of component communication for multimedia applications Transcoding support (On-going)

Component Remoting Technology Map

Switching support of component communication using network processors Switching mechanism supports Remote Object Invocation,.Net Remoting and Java RMI. The switching mechanism is implemented on IXP1200. Porting the switching mechanism to IXP2400. Future work: Parsing header, transcoding

Hardware comparison IXP1200IXP2400 PlatformRadisys ENP-2505Radisys ENP-2611 CoreStrongARM_232MhzXscale_600Mhz MicroEngine/thread6/48/8 RAM size Scratchpad-4KB SRAM-8MB DRAM-128MB Scratchpad-16KB SRAM-8MB DRAM-256MB I/O4 10/100 EtherNet Ports3 Gigabit optical ports New featureScratch Ring, Next Neighbor register porting

Two mode of NNR: Date can be read by next ME (ex. ME0:0 write data into a NNR, ME0:1 can read data from its NNR. ) Use as extra GPR NNR are useful when two pipeline stages are communicating. Next Neighbor Register ME Cluster 0 ME 0:0 ME 0:1 ME 0:2 ME 0:3 ME Cluster 1 ME 1:0 ME 1:1 ME 1:2 ME 1:3

Behavior of Packet Receiving 1.Divide packet into mpackets 2.Store Mpackets into DRAM 3.Gather metadata from Mpacket 64Byte DRAM SOP EOP Metadata of packet ScratchPad RAM Metadata format dl_buf_handle //The current buffer containing SOP dl_eop_buf_handle // for large packets, the buffer containing EOP. input port // port from which the packet is rxed …

… Ring Descriptors head tail base Size=128 Scratchpad RAM … Ring data Size = 128 Scratch Ring SRAM

Blueprint Ingress: one thread to receive packets from one 100 Mbps Ethernet port Egress: a scheduler thread loads the packets from the packet queues of each port in round-robin fashion L2 Bridge: relays and filters frames L3 Forwarder: forwards packets based on a forwarding table Stack ACE: allows I/O to and from the TCP/IP stacks and ACEs Load Balancer: distributing requests to servers according to servers ’ load StrongARM Ingress ACE Stack ACE L2 Bridge Load Balancer L3 Forwarder Egress ACE Linux TCP/IP Stack ME 0 Ingress Microcode ME 5 Egress Microcode ME 1 L2LBL3 ME 2 L2LBL3 ME 3 L2LBL3 ME 4 L2LBL3 Resource Manager

New Blueprint for IXP2400(Microengine) ME 0:0 Packet Rx Microcode ME 0:1 De-capsulateForwardLoad-balancer ME 0:2 De-capsulateForwardLoad-balancer ME 0:3 De-capsulateForwardLoad-balancer ME 1:0 Packet QM Microcode ME 1:1 Packet Scheduler Microcode ME 1:2 Packet Tx Microcode ME 1:3 Packet Tx Microcode Communication with Core components Use Neighbor Register

Progress What is done Microcode New blueprint of switching mechanism on IXP2400 Todo Core component Performance measure