1 / 31

Operating System Support for Network Control a virtual network interface approach for end-host OSs

Operating System Support for Network Control a virtual network interface approach for end-host OSs. Takashi Okumura WIDE Project / Asahikawa Medical College. Daniel Mossé University of Pittsburgh. Masaki Minami Keio University. Osamu Nakamura Keio University. Contents. Introduction

africa
Download Presentation

Operating System Support for Network Control a virtual network interface approach for end-host OSs

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. Operating System Support for Network Controla virtual network interface approach for end-host OSs Takashi OkumuraWIDE Project / Asahikawa Medical College Daniel MosséUniversity of Pittsburgh Masaki MinamiKeio University Osamu NakamuraKeio University

  2. Contents • Introduction • Control Model • Implementation & Performance • Conclusion

  3. Introduction- The problem we addressed -

  4. Priority inversion problem in network Low priorityprocess High priorityprocess • Need for Network Control Service by End-Host OS Userland Kernel Network Interface

  5. Dummynet, ALTQ, LTS MS QoS Manager netnice Some implementations, but... • No work has explored this issue in the context of design principle of operating systems...

  6. ? Dummynet, ALTQ, LTS netnice Need for a Resource Protection Model ?

  7. Per-flow Per-process Per-thread Need for Flexible Control Granularity • Per-Flow control, Per-Process control, Per-* control...

  8. Various types of network control WeightedFairQueuing Priority Queuing Token Bucket Work-conserving: PQ, WFQ, etc... Non Work-conserving: LB, TB, etc...

  9. Useful System Interface • Need a API that enables various controls in a single scheme.

  10. Control Model- How OS support for Network Control should be realized -

  11. BEFORE AFTER VIF : Virtual Network InterFace An Alternative Approach • Virtualization of network interfaces!!

  12. What VIF provides (1) • Hierarchical Resource Protection Model

  13. What VIF provides (2) • Flexible Control Granularity

  14. What VIF provides (3) • Realization of various network control Packet shaping Fair Queuing

  15. 2002 2003 VIF_1 fxp0 fxp0 netnicecommand % netnice -i fxp0 2002 64Kbps

  16. netniced HTML CGI Pseudo-stream Packet Shaper Priority Queue http stream Constant Bit Rate Stream netniceddaemon • Quality of Service Manager for VIF kernel httpd 45Mbps

  17. Implementation & Performance

  18. 100 101 /proc 100/ 101/ network/ VIF_1 VIF_2 fxp0 lo0/ files sockets/ fxp0/ lo0@ fxp0@ VIF_1/ VIF_2/ params params System Interface: procfs • Protection semantics is given by file access control...

  19. Kernel Module userland Transport Input Transport Output Network Input Network Output Struct ifnet Hierarchical Packet Scheduler ipintr Interface Input Interface Output Device Input Device Output kernel

  20. VIF Throughput

  21. VIF Delay

  22. Syscalls (in msec)

  23. Conclusion

  24. How OS support for network control should be realized • Through virtualization of network interfaces! AFTER BEFORE

  25. Advantages • Hierarchical resource protection • Flexible control granularity • Various types of network control • Simple, but powerful, API Realized at reasonable cost,for general-purpose Operating Systems.

  26. Thank you for listening!! http://www.asahikawa.wide.ad.jp/netnice/

  27. Abstraction of communicationvsVirtualization of network interface

  28. Network Perspective: Low-level abstraction • OS Perspective: High-level abstraction Abstraction of Communication Flows • What is it • Two perspectives

  29. Lack of system protection • Scalability problem • Lack of user knowledge ? Network Perspective OS should provide unified resource management scheme!!

  30. Lack of controllability of remote resources • Difficulty in the separation of system functionality • Lack of a simple API for various topologies and protocols ? ? ? ? ? ? Operating System Perspective High-level abstraction for communication flow is not easy!

  31. Low(network) High(OS) ? Abstraction of Communication Flows, Revisited. OS support for network contorl requires a new paradigm for its design principle...

More Related