DOC PREVIEW
Berkeley COMPSCI 162 - Lecture 1 What is an Operating System?

This preview shows page 1-2-3-4 out of 12 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Page 1CS162Operating Systems andSystems ProgrammingLecture 1What is an Operating System?January 23, 2008Prof. Anthony D. Josephhttp://inst.eecs.berkeley.edu/~cs162Lec 1.21/23/08 Joseph CS162 ©UCB Spring 2008Who am I?• Professor Anthony D. Joseph– 465 Soda Hall (RAD Lab)– adj AT cs.berkeley.edu– Office hours M 1pm/Tu 2pm in 413 Soda• Background:– MIT undergrad and grad student• Research areas:– Current: Network security, OS security, building a large security testbed, attacks against machine learning algorithms– Other: Mobile computing, wireless networking, cellular telephonyLec 1.31/23/08 Joseph CS162 ©UCB Spring 2008Goals 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 areadapted from slides ©2005 Silberschatz, Galvin, and Gagne. Slides courtesy of Kubiatowicz, AJ Shankar, George Necula, Alex Aiken, Eric Brewer, Ras Bodik, Ion Stoica, Doug Tygar, and David Wagner.Lec 1.41/23/08 Joseph CS162 ©UCB Spring 2008Rapid Underlying Technology Change• “Cramming More Components onto Integrated Circuits”– Gordon Moore, Electronics, 1965Page 2Lec 1.51/23/08 Joseph CS162 ©UCB Spring 2008Computing Devices EverywhereLec 1.61/23/08 Joseph CS162 ©UCB Spring 2008Computer 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 cyclesLec 1.71/23/08 Joseph CS162 ©UCB Spring 2008People-to-Computer Ratio Over TimeFrom David CullerLec 1.81/23/08 Joseph CS162 ©UCB Spring 2008Increasing Software ComplexityFrom MIT’s 6.033 coursePage 3Lec 1.91/23/08 Joseph CS162 ©UCB Spring 2008But, Latency Improves Slowly…From MIT’s 6.033 courseLec 1.101/23/08 Joseph CS162 ©UCB Spring 2008Heat is a Major Problem!From MIT’s 6.033 courseLec 1.111/23/08 Joseph CS162 ©UCB Spring 2008• How to manage complexity at all levels?• Many issues and many tradeoffs• Need a global view of systems– Decompose into components• Need a global understanding of systems– Applications, networks, databases, operating systems, security, software engineering…ComplexityLec 1.121/23/08 Joseph CS162 ©UCB Spring 2008Example: 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• Can’t hit reset button very easily!– Must reboot itself if necessary– Always able to receive commands from Earth• Individual Programs must not interfere– Suppose the MUT (Martian Universal Translator Module) buggy– Better not crash antenna positioning software!• Further, all software may crash occasionally– Automatic restart with diagnostics sent to Earth– Periodic checkpoint of results saved?• Certain functions time critical:– Need to stop before hitting something– Must track orbit of Earth for communicationPage 4Lec 1.131/23/08 Joseph CS162 ©UCB Spring 2008How do we tame complexity?• Every piece of computer hardware different– Different CPU» Pentium, PowerPC, ColdFire, ARM, MIPS– Different amounts of memory, disk, …– Different types of devices» Mice, Keyboards, Sensors, Cameras, Fingerprint readers– Different networking environment» Cable, DSL, Wireless, Firewalls,…• Questions:– Does the programmer need to write a single program that performs many independent activities?– Does every program have to be altered for every piece of hardware?– Does a faulty program crash everything?– Does every program have access to all hardware?Lec 1.141/23/08 Joseph CS162 ©UCB Spring 2008OS Tool: 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)ApplicationOperating SystemHardwarePhysical Machine InterfaceVirtual Machine InterfaceLec 1.151/23/08 Joseph CS162 ©UCB Spring 2008Interfaces Provide Important Boundaries• Why do interfaces look the way that they do?– History, Functionality, Stupidity, Bugs, Management– CS152  Machine interface– CS160  Human interface– CS169  Software engineering/management• Should responsibilities be pushed across boundaries?– RISC architectures, Graphical Pipeline Architecturesinstruction setsoftwarehardwareLec 1.161/23/08 Joseph CS162 ©UCB Spring 2008Course Administration• Instructor: Anthony D. Joseph (adj@cs)465 Soda Hall (RAD Lab)Office Hours (TBA): 413 Soda Hall• TAs: Barret Rhoden (cs162-tj@cory)Manu Srivastava (cs162-tk@cory)Man-Kit Leung (cs162-tl@cory)• Labs: Second floor of Soda Hall (poll)• Website: http://inst.eecs.berkeley.edu/~cs162• Webcast/Podcast (3-day delay):http://webcast.berkeley.edu/courses/index.php• Newsgroup: ucb.class.cs162 (use authnews.berkeley.edu)• Course Email: cs162@cory• Reader: Available from TBA• Are you on the waitlist? See Michael-David in 379 SodaPage 5Lec 1.171/23/08 Joseph CS162 ©UCB Spring 2008Class Schedule• Class Time: M/W 4 – 5:30pm, 277 Cory– Please come to class. Lecture notes do not have everything in them. The best part of class is the interaction!• Sections:– Important information is in the sections– The sections assigned to you by Telebears are temporary!– Every member of a project group must be in same sectionSection Time Location TA101Th 10:00-11:00A45 EvansBarret102Th 11:00-12:00P85 EvansBarret103Th 4:00-5:00P3102 EtcheverryMan-Kit104F 2:00-3:00P310 SodaManu105F 3:00-4:00p405 SodaManuLec 1.181/23/08 Joseph CS162 ©UCB Spring 2008Textbook• Text: Operating Systems Concepts, 7thEdition Silbershatz, Galvin, Gagne • Online supplements– See “Information” link on course website– Includes Appendices, sample problems, etc• Question: need 7thedition? – No, but has new material that we may cover– Completely reorganized– Will try to give readings from both the 6thand 7theditions on the lecture pageLec 1.191/23/08 Joseph CS162


View Full Document

Berkeley COMPSCI 162 - Lecture 1 What is an Operating System?

Documents in this Course
Lecture 1

Lecture 1

12 pages

Nachos

Nachos

41 pages

Security

Security

39 pages

Load more
Download Lecture 1 What is an Operating System?
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Lecture 1 What is an Operating System? and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Lecture 1 What is an Operating System? 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?