EECS 482 Introduction to Operating...

EECS 482Introduction to

Operating Systems

Winter 2018

BarisKasikcibarisk@umich.edu

(Thanks,HarshaMadhyastha fortheslides!)

January3,2018 EECS482– Lecture1 1

AboutMe

•Prof.Kasikci(Prof.K.),Prof.Baris(Prof.Barish)•AssistantProfessor• JoinedMichiganinFall’17• PhDfromEPFL• Previously,researcheratMicrosoftResearch• Previously,anembeddedsystemsdeveloper

• Interests:systemreliability,security,performance• EmployamixofmethodsfromOperatingSystems,ProgrammingLanguages,SoftwareEngineering,ComputerArchitecture

EECS482– Lecture1January3,2018 2

AboutYou

•Pleasetakeaselfieansendmenowtobarisk@umich.edu•Pleasecontacteecs482@umich.edu ifyouneedspecialarrangementforanydisabilities•Cometalktome• BBB4816,mydoorisalwaysopen• Anytimeaboutcareer,life,anydifficultiesyouarefacing,harddecisions,etc.• Duringofficehoursabout482

EECS482Staff

• Instructors•GSIs&IAs

AgendaforToday

•Whydoweneed482?

•Coursesyllabusandlogistics

•WhydoweneedanOSandwhatdoesitdo?

•HowdidOSesevolvetowhatwehavetoday?

Neuronstosilicon?

High-LevelCode

MachineInstructions

Processors

EECS280,281(programming)

EECS483(compilers)

EECS370(comp.organization)

EECS270(digitaldesign)

Whatismissing?

•Bootstrapping:• Howdoesacomputerstartwhenyouturniton?• HowtogetaprogramintomemoryandhavetheCPUstartexecutingit?

•ConcurrentexecutionwithI/O:• Howtoreadkeyboardormouse?Printoutputtoscreen?• Howtorunmultipleprogramsatthesametime,withoutonebreakingtheother?

•Persistenceandsecurity:• Howtosaveyourdatawhenyouturnthecomputeroff?• Howtopreventotherusersfromaccessingyourdata?• Howcanmultipleusersusethesamecomputersecurely?

Whatismissing?

•Bootstrapping:• Howdoesacomputerstartwhenyouturniton?• HowtogetaprogramintomemoryandhavetheCPUstartexecutingit?

•ConcurrentexecutionwithI/O:• Howtoreadkeyboardormouse?Printoutputtoscreen?• Howtorunmultipleprogramsatthesametime,withoutonebreakingtheother?

•Persistenceandsecurity:• Howtosaveyourdatawhenyouturnthecomputeroff?• Howtopreventotherusersfromaccessingyourdata?• Howcanmultipleusersusethesamecomputersecurely?

YouwillbeabletoanswerallthesequestionsbytheendofEECS482

Objectivesofthisclass

•Wewillunderstandprinciplesofconcurrency• Oneparadigm:multi-threadedprogram• Principlesapplytootherforms(e.g.,event-based)

•WewillstudydesignprinciplesofanOS• ThiscourseisnotaboutspecificsofanyparticularOS

•WewilldevelopanunderstandingofOSimpactonapplicationperformanceandreliability• WhatcausesyourprogramtocrashwhenyoudereferenceNULL?• Howcanmultithreadedcodebeslowerthansingle-threadedcode?

Prerequisites

•EECS281•EECS370•ExtensiveC/C++programmingexperience(STL)•FamiliaritywithUNIX•Understandingofcomputerarchitecture

• Stackpointer• Programcounter• Low-levelexecutionofaprogram• Etc.

•Someunderstandingofpaging,TLB,caching

ClassHomepageandTools

•Classwebpage• http://web.eecs.umich.edu/~harshavm/eecs482/• Syllabus,slides,homework,etc.postedonclasswebpage• SubscribetoPiazza!• Announcementsandclassdiscussion

LectureSchedule

•CPU(threadsandconcurrency)•Memory(addressspaces)•Midterm•Network(sockets)•Storage(filesystems)•Aggregation:distributedsystemsandcasestudies

Lectures

•2sections• Mostlysynchronized,examswillhaveafewdifferentquestions

• Lecturecaptured(videosonline)

•Slidesandlecturenoteswillbepostedonthewebpage

•Textbook(highlyrecommended):• AndersonandDahlin,“OperatingSystems:PrinciplesandPractice”• Additionalreadingspostedonthewebpage

Lab/DiscussionSections

•OKtoattendanydiscussion• Aslongasthereareseats

Questionspostedseveraldaysinadvance• Dothembefore goingtoyoursection• Thispreparesyouwellforexams• Coverssomebackgroundknowledge

•NoDiscussionSessionsThisFriday!

Projects

•4projects• Writingaconcurrentprogram• Threadmanager• Virtualmemorypager• Multi-threadedsecurenetworkfilesystem

•Firstisindividual,doothersingroupsof2-3• RegisteryourGitHubid– we’llassignrepositories• Declareyourgroup(by1/22)viacoursewebpage• Maileecs482@umich.edu iftaken482before• Can’treuseanycodeexceptforproject1.

Projectrecommendations

•Choosegroupmemberscarefully• Checkschedule,classgoals,style,etc.• UsePiazzatofindgroupmembers

•We’llevaluateeverymember’scontributions• Peerfeedback• gitlogandGitHubstatistics

•Groupcanfireoneofitsmembers(seesyllabus)

ProjectsareHARD!

•ProbablythehardestclassyouwilltakeatUMintermsofdevelopmenteffort• Projectswilltake95%ofyourtimeinthisclass

•Reasonforbeinghard:• Notnumberoflinesofcode!• Instead,newconcepts:threads,interrupts,addressspaces,namespacesetc.

Projectrecommendations

•Donotstartworkingonprojectsatlastminute!• Projectsareautograded(mustbemostlycorrect)• No.ofhoursyouputinorlinesofcodedon’tcount• Testingisintegralprocessofdevelopment

•Makegooduseofhelpavailable• ~20officehoursperweek(extrahourswhenprojectsaredue)• Therewillbelongqueues• MonitorandparticipateindiscussiononPiazza• Hintsduringlectures,discussions(alsointextbook!)

Policies

•Submission• 1submissionperdaytoautograder+3bonus• Dueatmidnight(harddeadline!)• 3latedaysbudgetacrossallprojects(ifyouhandinyourprojecttwodayslate,youwillhaveonelatedayleft)

•Collaboration• OkaytoclarifyproblemordiscussC++syntax• Notokaytodiscusssolutions• Pastsolutionsarealproblem(severalHCcases)

Exams(Tentative!)

•Midterm:February21st (6:30-8:30pm)

•Final:April23th (7-9pm)

•Nomakeupexams• Unlessdirecircumstances• Makesureyouscheduleinterviewsappropriately• E-mailme(eecs482@umich.edu)withexceptions/conflicts

Gradingbreakdown

•Projects:• Project1:3%• Projects2,3,and4:15%each

•Mid-term:26%•Final:26%

Enrollment

Musthaveprerequisites(281&370orequivalent)

Overrides• Currentlynearcapforcoursestaffing• Hopemanycanenrollduetonormalchurn

Protipsforsuccessin482

•Startearlyonprojects

• LeverageGitHubandcommunicatewithteam

•Takeadvantageofavailablehelp• Gotoofficehours,post/monitorquestionsonPiazza

•Attendlecturesanddiscussions• Readtextbook,solvequestionsbeforediscussion

•Askquestionswhensomethingisunclear

WhyhaveanOS?

•Whatifapplicationsrandirectlyonhardware?

•Problems• Portability• Resourcesharing

Applications

Hardware

WhatisanOS?

•Theoperatingsystemisthesoftwarelayerbetweenuserapplicationsandthehardware

•OSis“allthecodethatyoudon’thavetowrite” toimplementyourapplication

OperatingSystem

Hardware

ApplicationsVirtualMachineInterface

PhysicalMachineInterface

RolesoftheOS

• Illusionist:Createabstractions• CPUà Threads• Memoryà Addressspace

•Government:Managesharedhardwareresources• Butatacost(taxes)

•ForanyareaofOS,ask• Whatinterfacedoeshardwarepresent?• WhatinterfacedoesOSpresenttoapplications?

OSandApps:2Perspectives

•Perspective1:applicationismainprogram• Getsservicesbycallingkernel(OS)• Example:printthistothescreen

•Problemswiththisview:• Howdoesapplicationstart?• Howdotasksoccurringoutsideanyprogram(e.g.receivingnetworkpackets)getdone?• Howdomultipleprogramsrunsimultaneouslywithoutmessingeachotherup?

OSandApplications

•Perspective2:OSismainprogram• Callsapplicationsassubroutines• Illusion:everyapprunsonitsowncomputer

• Lowerlayer(OS)invokeshigherlayer(apps)!•ApporprocessorreturnscontroltoOS•Correctperspective,butwhatisitthatmakestheOSthe“main”program?

WhytakeanOSclass?- 1

•Masteringconcurrency• Performancetodayachievedthroughparallelism• Masteryrequiredtobeatop-notchdeveloper

•Understandingwhatyouuse• UnderstandingtheOShelpsyouwritebetterapps• Functionality,performancetuning,simplicity,etc.

•Universalabstractionsandoptimizations• Caching,indirection,naming,atomicity,protection,…• Examples:Cloudcomputing,Webservices,mobile

WhytakeanOSclass?- 2

•BuildanOS•Conceptsreusedinmanyapplications• Google’swebserverfarm• AmazonWebServices(time-shared)• Hypervisors(VMWareESXserver)• NVDIAdevicedriver

•Softwaredevelopment• Designanabstraction• Makeitefficientlyusablebyothers

•Design-relatedinterviewquestions

Historyofoperatingsystems

•Singleoperatoratconsole

•Positives:• Interactive• Verysimple

•Downside:• Poorutilizationofexpensivehardware

humanI/OCPUI/OhumanI/OCPU

•Batchprocessing(usingpunchcards)• Goal:ImproveCPUandI/Outilizationbyremovinguserinteraction

•OSisbatchmonitor+libraryofstandardservices•Protectionbecomesanissue• Whywasn’tthisanissueforsingleoperatoratconsole?

•Notinteractive

timeI/OCPUI/OCPUI/OCPU

https://www.wired.com/2015/07/hackers-remotely-kill-jeep-highway/

•Multi-programmedbatch• ImproveutilizationbyoverlappingCPUandI/O

P1:CPUDiskCPUPrint

P2:DiskCPUPrintCPUPrint

P3:DiskCPU

•Multi-programmedbatch• ImproveutilizationbyoverlappingCPUandI/O

P1:CPUDiskCPUPrint

P2:DiskCPUPrintCPUPrint

P3:DiskCPU

OSbecomesmorecomplex!• Runsmultipleprocessesconcurrently• EnablessimultaneousCPUandI/O•MultipleI/Ostakeplacesimultaneously• Protectsprocessesfromeachother• But,stillnotinteractive

•Timesharing• Goal:Allowpeopletointeractwithprogramsastheyrun• Insight:Usercanbemodeledasa(veryslow)I/Odevice• Switchbetweenprocesseswhilewaitingforuser

P1:CPUDiskCPUPrint

P2:UserCPUUserCPUUser

P3:User DiskCPU

•Timesharing• Goal:Allowpeopletointeractwithprogramsastheyrun• Insight:Usercanbemodeledasa(veryslow)I/Odevice• Switchbetweenprocesseswhilewaitingforuser

P1:CPUDiskCPUPrint

P2:UserCPUUserCPUUser

P3:User DiskCPU

OSisnowevenmorecomplexLotsofsimultaneousjobsMultiplesourcesofnewjobs(peoplecanstartnewjobs)Interactivityisrestored

•OSstartedoutverysimple• Becamecomplextousehardwareefficiently

•ConsiderPCsandworkstations:• Isthemainassumption(hardwareisexpensive)stilltrue?

•HowdoesthisaffectOSdesign?• Don’tPCsneedtotimesharebetweenmultiplejobs?• Don’tPCsneedprotectionbetweenmultiplejobs?

PCsgraduallyaddedbacktime-sharingfeatures

Whatabouttoday?

•Cloudcomputing(e.g.AmazonEC2)• Ishardwareexpensive?• WhatotherOSfeaturesareneeded?

•Mobilecomputing(e.g.,Android/iOS)• Whatdrivesefficiency?• WhatOSfeaturesareneeded?

QuestionstoPonder

•Somewhatsurprisingly,OSescontinuetoevolve• WhatarethedriversofOSchange?• Newhardware,security,energy

•WhatispartofanOS?Whatisnot?• IsthewindowingsystempartofanOS?• OSresearchhasbecomeDist.Systemsresearch

Linuxvirtualmemorysystemoverhaul:https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/

•Browsethecoursewebpage

•SubscribetoPiazza

•RegisteryourGitHubid

•Startfindingpartnersforprojectgroup(Jan22)

EECS 482 Introduction to Operating...

Documents

Transcript of EECS 482 Introduction to Operating...

482 bk0081

EECS 311: Chapter 2 Notes Chris Riesbeck EECS Northwestern.

GRADUATE DEGREE PROGRAMS in COMPUTER SCIENCE AND ENGINEERING - Home | EECS … · · 2016-09-12graduate degree programs in computer science and engineering ... eecs 482, eecs 483,

Edição 482

Optimization Models - EECS 127 / EECS 227AT

482 bk0080

EECS 482 Introduction to Operating Systemsweb.eecs.umich.edu/~harshavm/eecs482/lec1_handouts/lec21... · 2018. 3. 28. · March 26, 2018 EECS 482 –Lecture 22 27. Endianness ...

EECS Department

EECS 482 Introduction to Operating Systems

EECS 482 Introduction to Operating Systemsweb.eecs.umich.edu/.../section1/lec12_eviction-pre.pdfmemory addresses (e.g., to refer to translation data)? Feb 25, 2019 EECS 482 –Lecture

482 guaixe

EECS 582 Introduction Mosharaf Chowdhury EECS 582 – W1611/6/16.

EECS 482 Introduction to Operating Systemsweb.eecs.umich.edu/.../section1/lec11_paging-final.pdfDifferent segments can have different protection • E.g., code is usually read only

protostypos 482

482 - minsalud.gov.co³n No. 482 de... · Title: 482 Created Date: 2/22/2018 3:50:14 PM

Agenda 482

EECS 482 Introduction to Operating Systemsweb.eecs.umich.edu/~manosk/eecs482/handouts/... · Slides by: Harsha V. Madhyastha. Recap ... • Save private state in TCB to resume execution

EECS 1030 moodle.yorku€¦ · Chapter 6: Inheritance EECS 1030 moodle.yorku.ca moodle.yorku.ca EECS 10301/15

edicion 482

EECS 482 Introduction to Operating Systemsweb.eecs.umich.edu/~harshavm/eecs482/lec1_handouts/lec17_fs.pdf · Indexed files File = array of block pointers • Just like page table