Ubiquitous Component Remoting Support on Overlay Network - PowerPoint PPT Presentation

About This Presentation
Title:

Ubiquitous Component Remoting Support on Overlay Network

Description:

Ubiquitous Component Remoting Support on Overlay Network. Adaptation support with ... Ingress: one thread to receive packets from one 100 Mbps Ethernet port ... – PowerPoint PPT presentation

Number of Views:18
Avg rating:3.0/5.0
Slides: 12
Provided by: yhch
Category:

less

Transcript and Presenter's Notes

Title: Ubiquitous Component Remoting Support on Overlay Network


1
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)

2
Component Remoting Technology Map
3
(No Transcript)
4
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

5
Hardware comparison
porting
IXP1200 IXP2400
Platform Radisys ENP-2505 Radisys ENP-2611
Core StrongARM_232Mhz Xscale_600Mhz
MicroEngine/thread 6/4 8/8
RAM size Scratchpad-4KB SRAM-8MB DRAM-128MB Scratchpad-16KB SRAM-8MB DRAM-256MB
I/O 4 10/100 EtherNet Ports 3 Gigabit optical ports
New feature Scratch Ring, Next Neighbor register
6
Next Neighbor Register
  • Two mode of NNR
  • Date can be read by next ME (ex. ME00 write data
    into a NNR, ME01 can read data from its NNR. )
  • Use as extra GPR
  • NNR are useful when two pipeline stages are
    communicating.

ME Cluster 0
ME 00
ME 01
ME 02
ME 03
ME Cluster 1
ME 10
ME 11
ME 12
ME 13
7
Behavior of Packet Receiving
64Byte
  1. Divide packet into mpackets
  2. Store Mpackets into DRAM
  3. Gather metadata from Mpacket

0
64
149
DRAM
SOP
EOP
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
ScratchPad RAM
8
Scratch Ring
Scratchpad RAM
SRAM
Ring data Size 128

9
Blueprint
StrongARM
Linux TCP/IP Stack
Stack ACE
  • 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

Ingress ACE
L2 Bridge
Load Balancer
L3 Forwarder
Egress ACE
Resource Manager
ME 1
L2
LB
L3
ME 2
ME 0
ME 5
L2
LB
L3
Ingress Microcode
Egress Microcode
ME 3
L2
LB
L3
ME 4
L2
LB
L3
10
New Blueprint for IXP2400(Microengine)
Communication with Core components
Use Neighbor Register
11
Progress
  • What is done
  • Microcode
  • New blueprint of switching mechanism on IXP2400
  • Todo
  • Core component
  • Performance measure
Write a Comment
User Comments (0)
About PowerShow.com