1 / 25

Liquid Software

Liquid Software. Larry Peterson Princeton University John Hartman University of Arizona http://www.cs.princeton.edu/nsg/. Goals. Build a High-Performance Active Router no penalty for passive packets pay only for the extensibility you need Demonstrate “Active Search” Application

kimberley-peck
Télécharger la présentation

Liquid Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Liquid Software Larry Peterson Princeton University John Hartman University of Arizona http://www.cs.princeton.edu/nsg/

  2. Goals • Build a High-Performance Active Router • no penalty for passive packets • pay only for the extensibility you need • Demonstrate “Active Search” Application • Universal Search Interface (USI) • programmable query + aggregation in network

  3. Project Roadmap NetTV/NetCAM IP Router Next Generation Router Scout Web Server NodeOS Firewall Joust Active Search Q1/99 Time

  4. Scout OS • Targeted at Network Appliances • network-attached devices, proxies, … • Configurable • specialized for a particular appliance • Path Abstraction • encapsulates I/O flow through the system • Status • runs on Alpha and Pentium processors • currently distributing version 2.0

  5. NetTV • End-to-End Paths • - best effort • - realtime • Cycle Scheduler • - based on WFQ • - steal to meet deadlines NetTV RTP UDP IP MPEG ETH WIMP KBD VGA 3COM

  6. RSVP IP Eth Eth Best-effort Controlled-load Device Driver0 Device Driver1 IP Router • Link Schedulers • - RED • - RIO (DiffServ) • - WFQ

  7. Web Server • Resource Accounting • all cycles & memory • minimal overhead • Protection Domains • isolate untrusted code • at any module boundary • Policy • protect against denial of service • limit resource usage SCSI FS HTTP TCP IP ETH

  8. TCP TCP IP IP Proxy Firewall HTTP Proxy Net2 Net1

  9. Splicing Optimization IP++ Net2 Net1

  10. Firewall Performance Throughput (pps)

  11. Firewall Performance (cont) Throughput (pps)

  12. Joust JVM NFS • Status • - supports JDK 1.1.x • - runs on Scout, Linux, • Solaris, Irix • Toba Compiler • - WAT: Java-to-C • - JIT: on x86 RPC WIMP DNS TCP UDP IP ARP VGA KBD ETH

  13. Joust Performance Round Trip Latency (Microseconds)

  14. NodeOS • Multiplex Node Resources • Features • optimized to forward packets • fine-grained (per-flow) multiplexing • permit cut-through flows • access to OS/HW-specific features • Status • draft interface spec • prototype implementation Execution Environments ANTS PLAN JANE . . . NodeOS API Joust NodeOS Scout

  15. Next Generation Router • Extensible • Scalable • Open • Commodity Components • Performance • Robust

  16. Assumption Boundary R Untrusted Reliable High Latency High BW High Power DiffServ Trusted Flaky Low Latency Low BW Low Power IntServ Edge Routers R Rest of the Internet My Network

  17. Server Nodes Client(s) . . . R . . . . . . Balance Load Cache Data Protocol Translation Partition Data Stream Scalable Servers

  18. Router as LAN R R Authenticate Users Filter Packets Intrusion Detection

  19. Active Networks

  20. Routing software w/ router OS Routing software w/ COTS OS Line card (forwarding buffering) Routing CPU Buffer memory CPU Buffer memory Line card (forwarding buffering) Line card (forwarding buffering) ... NI as line card NI as line card NI as line card Line card (forwarding buffering) Traditional Routers • extensible • open • low throughput • not scalable • high throughput • not extensible • limited scalability • closed

  21. Key Ideas • Closer integration of... • processing cycles • switching bandwidth • Implement hierarchy of… • classification mechanisms • processing paths

  22. Katmai Katmai Katmai Katmai Katmai Katmai NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP CPU CPU CPU CPU CPU CPU . . . . . . . . . . . . . . . . . . MEM MEM MEM MEM MEM MEM NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP Hardware Architecture 200Gbps Crossbar Switch

  23. . . . . . . . . . . . . . . . . . . NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP NI with uP . . . . . . Katmai Katmai Katmai Katmai Katmai Katmai Katmai Katmai . . . . . . . . . CPU CPU CPU CPU CPU CPU CPU CPU MEM MEM MEM MEM MEM MEM MEM MEM 200Gbps crossbar switch 200Gbps crossbar switch 200Gbps crossbar switch 200Gbps crossbar switch . . . . . . . . . Scalable Router

  24. Slow/Programmable JIT EE (user space) Kernel . . . Line Card Hardware + e Hardware Fast/Fixed Hierarchy of Paths JIT Hardware Input Port Output Port

  25. Challenges • Refine Architecture • balance hardware configuration • partition functionality • Interfaces • hardware/OS • EE/OS (NodeOS Interface) • Scheduling and Resource Allocation • cycle and link bandwidth • multi-switch channels • protect against denial-of-service attacks

More Related