Download 投影片 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)
Component
Remoting
Component
Remoting
Technology Map
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
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
Next Neighbor Register

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.
ME 0:0
ME 0:1
ME 0:2
ME 0:3
ME 1:2
ME 1:3
ME Cluster 0
ME 1:0
ME 1:1
ME Cluster 1
Behavior of Packet Receiving
64Byte
1.
2.
3.
Divide packet into
mpackets
Store Mpackets into
DRAM
Gather metadata
from Mpacket
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
…
…
0
64
149
DRAM
SOP
ScratchPad RAM
Metadata of packet
EOP
Scratch Ring
Scratchpad RAM
SRAM
Ring Descriptors
0
1
2
…
15
head
tail
base
Size=128
Ring data
…
Size = 128
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
Linux
TCP/IP
Stack
Ingress
ACE
L2
Bridge
Stack
ACE
Load
Balancer
L3
Forwarder
Egress
ACE
Resource Manager
ME 1
L2
LB
L3
LB
L3
ME 2
ME 0
L2
Ingress
Microcode
ME 5
Egress
Microcode
ME 3
L2
LB
L3
LB
L3
ME 4
L2
New Blueprint for
IXP2400(Microengine)
Communication with
Core components
ME 1:1
Packet
Scheduler
Microcode
ME 0:1
De-capsulate
ME 0:0
Packet Rx
Microcode
ME 1:2
Forward
Load-balancer
ME 1:0
ME 0:2
De-capsulate
Use Neighbor
Register
Forward
Load-balancer
Packet Tx
Microcode
Packet QM
Microcode
ME 1:3
Packet Tx
Microcode
ME 0:3
De-capsulate
Forward
Load-balancer
Progress

What is done



Microcode
New blueprint of switching mechanism on
IXP2400
Todo


Core component
Performance measure