1 / 14

Writeup

Given the critical role of fault tolerance (FT) in computing, this discussion explores strategies across hardware, OS, and application levels. We analyze the structure of scalable operating systems, defining local and global OS functions, and their services. Key functionalities, such as process management, file systems, and security, are examined in the context of scalability and performance, particularly on heterogeneous architectures including FPGAs and PIMs. We also address the implications of hardware features on OS design and discuss benchmarks for assessing OS success.

rhoda
Télécharger la présentation

Writeup

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. Writeup

  2. Fault tolerance • Given that FT is critical, what could/should be done at hw/os/runtime/app level? • ALL

  3. Structure of Scalable OS • What are the entities? • How we define local/global OS functions • What is the functionality of the local OS services? Is none an answer? • What are global functions? • Can we adapt PVM to the app it supports? • Protection boundaries and virtualization with OS • What’s OS/runtime split? • ALL

  4. APIs • Runtime/OS • Application/runtime • Tool interfaces (including debugging) • Interfaces to environment info • 10

  5. Specific functions • Process management 9 • File system 18 • Scheduling 10 • Security 2 • QoS 2 • Debugging – invariants 9

  6. OS scalability • What OS services could/should scale • How do we define scalability? • performance nearly independent of machine size? • reliability nearly independent of machine size • 10

  7. OS for heterogeneous hw • How do we build runtime/OS support for “crazy” architectures? • FPGAs, PIMs,… • Do we adapt one parallel OS to very different hw architectures? Do we need different OS/runtime solutions? • What is the spectrum of hw architectures that we can support with one common OS/runtime design? • 15

  8. Interactive systems • How do we move HEC into interactive environments? • What are interactive HEC apps? • How do we do interactive debugging? Interactive tools? Interactive computational steering? Short shell commands? WS acceleration model? Visualization? • 12

  9. Hw support for OS • Study which hw features are important to future scalable OS/runtime – so as to influence hw design; E.g. • Protection • Reliable networks • Collective ops • Atomic memory ops • Transactional memory • 16

  10. Application requirements • What OS calls are now used by High Perf Apps? • What requirements can we derive for OS/runtime in future systems from apps? • Identify critical apps we care about • 14

  11. OS metrics • What benchmarks and metrics we use to measure success? • 8

  12. Programmatic • How we get organized to do research in scalable OS? • Multiple approaches • Extreme alternatives • Vendor involvement 12

  13. Vendors • How can we use existing OS sw • Proprietary and/or open source • 8

  14. Testbeds • How do we establish testbeds to support scalable OS/runtime research • Who funds them • What is a testbed? Architecture specific? Simulator? • 15

More Related