How outscale/packetgraph works
Main Components
a) Core Components:
• DPDK Integration Layer
• Packet Processing Engine
• Brick Management System
• Graph Management System
• Thread Management System
b) Brick Types (Group by functionality):
• Layer 2 Components (Switch, Hub)
• Virtual Interfaces (TAP, VHOST)
• Security Components (Firewall, Antispoof)
• Tunneling (VTEP)
• Utility Components (Print, Queue, Diode)
• Network Interface (NIC)
• Custom Components (User-dipole, RXTX)
┌─────────────────────────────────────────────────────────┐
• Application Layer │
• ┤
• Packetgraph Core │
• ┬───────────┬────────────┬──────────────────┤
• Graph │ Brick │ Thread │ Packet │
• Manager │ Manager │ Manager │ Processing │
• ┴───────────┴────────────┴──────────────────┤
• DPDK Interface │
• ┘
Component Relationships
• Data flow (→): Show packet movement between bricks
• Dependencies (⇢): Show component dependencies
• Control flow (⇒): Show management operations
Brick Components Section
┌─────────────────── Brick Types ──────────────────┐
• ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
• Network │ │Security │ │ Virtual │ │ Utility │ │
• Bricks │ │ Bricks │ │ Bricks │ │ Bricks │ │
• ┘ └─────────┘ └─────────┘ └─────────┘ │
• ┘
Implementation Details
Technical details such as:
• Maximum burst size (64 packets)
• Thread safety boundaries
• Core affinity
• Huge page memory allocation
• DPDK PMD integration