1 / 7

Concurrency Conclusion

Since 1985, major OSs come with threads for better abstraction. MS OS/2's thread-heavy design led to failure due to inefficiencies and high memory costs. Learn why threads are important but not free.

unar
Download Presentation

Concurrency Conclusion

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. Concurrency Conclusion Andy Wang Operating Systems COP 4610 / CGS 5765

  2. Threads and Synchronization • Better, cleaner, and simpler abstraction to application programmers

  3. Since 1985 • Every major OS comes with threads • Mach • OS/2 • Windows XP, NT, 7, 8, 10 • Vista • Solaris • Mac OS X • iOS • Android

  4. Since 1985 • Major applications are written in threads • Word processing • Databases • Web servers • Embedded systems

  5. A Cautionary Tale • Microsoft OS/2 • Spectacular failure • IBM re-wrote the whole OS from scratch • Used threads for everything • Window systems • Communication among programs

  6. Microsoft OS/2 • Created many threads • Few are ready to run • Most threads wait around for user typing and network packets • Since each thread needs to store its own execution stack (running or waiting), OS/2 required $200 extra memory to store those threads • $200 for working while printing?

  7. The Moral of the Story… • Threads are cheap • But they are not free

More Related