CPS110 / EE 153: Intro to Operating Systems. Jeff Chase August 25, 2008. About the guy I got these slides from (Landon Cox). Background BS Math/CS: Duke, ’99 PhD EECS: Michigan, ’05 Research interests OS, p2p, economics, security, mobility Why am I a professor?
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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
CPS110 / EE 153: Intro to Operating Systems
August 25, 2008
Some kind of B
Some kind of A
high-level programming languages
compiling, reading programs off disk, getting program into memory, reading keyboard, starting the computer, saving files, filenames, networking
Assembly language program
What interface does the OS present?
What interface does the hardware present?
Load/store, mem, regs
OS runs first, calls program
Programs run until they return control to OS
(by themselves or forced by hardware)
Then OS calls another program
How do programs start?
Tasks outside program? (net recv)
How to prevent CPU hogging?
Key question: who calls whom?
Environment aka “the client”
What is wrong with this timeline?
CPU utilization is awful
Since CPUs were expensive, this mattered