class-reader - CS162 Operating Systems and Systems...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: CS162 Operating Systems and Systems Programming Lecture 1 What is an Operating System? August 28 th , 2006 Prof. John Kubiatowicz http://inst.eecs.berkeley.edu/~cs162 Lec 1.2 8/27/06 Kubiatowicz CS162 UCB Fall 2006 Who am I? Professor John Kubiatowicz (Prof Kubi) Background in Hardware Design Alewife project at MIT Designed CMMU, Modified SPAR C processor Helped to write operating system Background in Operating Systems Worked for Project Athena (MIT) OS Developer (device drivers, network file systems) Worked on Clustered High-Availability systems (CLAM Associates) Peer-to-Peer OceanStore project Store your data for 1000 years Tapestry and Bamboo Find you data around globe Quantum Computing Well, this is just cool, but probably not apropos Lec 1.3 8/27/06 Kubiatowicz CS162 UCB Fall 2006 Goals for Today What is an Operating System? And what is it not? Examples of Operating Systems design Why study Operating Systems? Oh, and How does this class operate? Interactive is important! Ask Questions! Note: Some slides and/or pictures in the following are adapted from slides 2005 Silberschatz, Galvin, and Gagne. Many slides generated from my lecture notes by Kubiatowicz. Lec 1.4 8/27/06 Kubiatowicz CS162 UCB Fall 2006 Rapid Underlying Technology Change Cramming More Components onto Integrated Circuits Gordon Moore, Electronics, 1965 Lec 1.5 8/27/06 Kubiatowicz CS162 UCB Fall 2006 Computing Devices Everywhere Lec 1.6 8/27/06 Kubiatowicz CS162 UCB Fall 2006 Computer System Organization Computer-system operation One or more CPUs, device controllers connect through common bus providing access to shared memory Concurrent execution of CPUs and devices competing for memory cycles Lec 1.7 8/27/06 Kubiatowicz CS162 UCB Fall 2006 Functionality comes with great complexity! Proc Caches Busses Memory I/O Devices: Controllers adapters Disks Displays Keyboards Networks Pentium IV Chipset Lec 1.8 8/27/06 Kubiatowicz CS162 UCB Fall 2006 Sample of Computer Architecture Topics Instruction Set Architecture Pipelining, Hazard Resolution, Superscalar, Reordering, Prediction, Speculation, Vector, Dynamic Compilation Addressing, Protection, Exception Handling L1 Cache L2 Cache DRAM Disks, WORM, Tape Coherence, Bandwidth, Latency Emerging Technologies Interleaving Bus protocols RAID VLSI Input/Output and Storage Memory Hierarchy Pipelining and Instruction Level Parallelism Network Communication Other Processors Lec 1.9 8/27/06 Kubiatowicz CS162 UCB Fall 2006 Example: Some Mars Rover Requirements Serious hardware limitations/complexity: 20Mhz powerPC processor, 128MB of RAM cameras, scientific instruments, batteries, solar panels, and locomotion equipment Many independent processes work together Cant hit reset button very easily!...
View Full Document

Page1 / 215

class-reader - CS162 Operating Systems and Systems...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online