1 / 10

FAST-OS Breakout Summary

FAST-OS Breakout Summary. David Greenberg Larry Kaplan Ron Brightwell Greg Czajkowski Rusty Lusk Al Geist Orran Krieger. Enablers. Modular Infrastructure/Framework for OS Research Make HPC research/experimentation easier to do Coordinate High Performance Linux “Distro”

rania
Download Presentation

FAST-OS Breakout Summary

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. FAST-OS Breakout Summary David Greenberg Larry Kaplan Ron Brightwell Greg Czajkowski Rusty Lusk Al Geist Orran Krieger

  2. Enablers • Modular Infrastructure/Framework for OS Research • Make HPC research/experimentation easier to do • Coordinate High Performance Linux “Distro” • Make sure base testset functions properly. • Develop APIs and coding practices • Supervise insertion of advanced ideas • More than just kernel • Do we need more than just Linux? • Simulator ala SIMOS

  3. Scientific/Reproducible Experiments • Parallel, Scalable, Accessable testbed of at least … nodes • Provision for running multiple OSes with full hardware access • Beyond x86 • Definition of metrics and benchmarks to define success. When do things work well as well as when do they work poorly.

  4. Ideas to Explore • OS/runtime support for safe languages (ala Java). • New local protection mechanisms • OS/runtime support for advanced/new languages. • OS/runtime interaction with novel hardware architectures. • I/O offloading

  5. Fault Management • General detection, notification, recovery • Ways of OS monitoring • For performance, resource use • Notification issues • How to maintain reliable transport in faulty situation • Can we define standard interfaces?

  6. Scope and Range • Define application OS service “working sets” • Facilitate OS prototype • Drive benchmarks • Guide app development • What new services are needed? • What semantics are the right ones if POSIX are not. • What is Middleware currently forced to do which should be done by OS/runtime.

  7. Issues I • Applications/User support for testing of novel ideas • How can we capture advances in non-HPC OSes • What new usage models for high-end machines are going to develop • How can we parameterize, customize our OS without bifurcating.

  8. Issues II • What are the right virtualization models. • How do we make performance portable OSes. • How can we assure that OS can take advantage of multiple hardware assists. • What are services which need to be scalable, how can we supply them. • What can OS do to improve application performance?

  9. Holy Grail, Way out, Long Term • How can OS autonomously adapt for performance, upgrade, security, fault tolerance.

  10. Suggestions • Companion program to fund applications use of new OS ideas. • Usenix, OLS, SOSP, OSDI • Beowulf mailing list, Slashdot, Linux kernel mailing lists, scalablility sublist • Tie to HPCS program, ASCI Pathforward, SCIDAC. How? Can make sure that still inclusive? • Provide descriptions of existing efforts. • How can call make environment for research clearly inviting?

More Related