聊城大学计算机学院计算机操作系统（2）英文课件 Lecture2.ppt

CS162Operating Systems andSystems ProgrammingLecture 2History of the World Parts 1—5 Operating Systems Structures August 31, 2005 Prof. John Kubiatowicz /~cs162 Review: What does an Operating System do? Silerschatz and Gavin: “An OS is Similar to a government” Begs the question: does a government do anything useful by itself? Coordinator and Traffic Cop: Manages all resources Settles conflicting requests for resources Prevent errors and improper use of the computer Facilitator: Provides facilities that everyone needs Standard Libraries, Windowing systems Make application programming easier, faster, less error-prone Some features reflect both tasks: E.g. File system is needed by everyone (Facilitator) But File system must be Protected (Traffic Cop) Review: Virtual Machine Abstraction Software Engineering Problem: Turn hardware/software quirks ?  what programmers want/need Optimize for convenience, utilization, security, reliability, etc… For Any OS area (e.g. file systems, virtual memory, networking, scheduling): What’s the hardware interface? (physical reality) What’s the application interface? (nicer abstraction) Review: Example of Address Translation Review: Dual Mode Operation Hardware provides at least two modes: “Kernel” mode (or “supervisor” or “protected”) “User” mode: Normal programs executed Some instructions/ops prohibited in user mode: Example: cannot modify page tables in user mode Attempt to modify ? Exception generated Transitions from user mode to kernel mode: System Calls, Interrupts, Other exceptions Goals for Today History of Operating Systems Really a history of resource-driven choices Operating Systems Structures Operating Systems Organizations Moore’s law change Typical academic computer 1981 vs 2005 Dawn of timeENIAC: (1945—1955) “The machine designed by Drs. Eckert and Mauchly was a monstrosity. When it was finished, the ENIAC filled an entire room, weighed thirty tons, and consumed two hundred kilowatts of power.” /~history/ENI