Operating Systems CSE 411 Revision and final thoughts Revision and final thoughts Dec. 15 2006 - Lecture 33 Instructor: Bhuvan Urgaonkar.

Slides:



Advertisements
Similar presentations
CSC 360- Instructor: K. Wu Overview of Operating Systems.
Advertisements

Operating System.
WHAT IS AN OPERATING SYSTEM? An interface between users and hardware - an environment "architecture ” Allows convenient usage; hides the tedious stuff.
Operating Systems ECE344 Ding Yuan Final Review Lecture 13: Final Review.
Threads, SMP, and Microkernels Chapter 4. Process Resource ownership - process is allocated a virtual address space to hold the process image Scheduling/execution-
Computer Systems/Operating Systems - Class 8
Review: Chapters 1 – Chapter 1: OS is a layer between user and hardware to make life easier for user and use hardware efficiently Control program.
CMPT 300: Final Review Chapters 8 – Memory Management: Ch. 8, 9 Address spaces Logical (virtual): generated by the CPU Physical: seen by the memory.
Winter 2005 CMPE 151: Network Administration Lecture 2.
Lecture 1: History of Operating System
OS Fall ’ 02 Introduction Operating Systems Fall 2002.
CMPT 300: Operating Systems Review THIS REIVEW SHOULD NOT BE USED AS PREDICTORS OF THE ACTUAL QUESTIONS APPEARING ON THE FINAL EXAM.
CMPT 300: Final Review Chapters 8 – Memory Management: Ch. 8, 9 Address spaces Logical (virtual): generated by the CPU Physical: seen by the memory.
OS Spring’03 Introduction Operating Systems Spring 2003.
Figure 1.1 Interaction between applications and the operating system.
1 Last Class: Introduction Operating system = interface between user & architecture Importance of OS OS history: Change is only constant User-level Applications.
OPERATING SYSTEMS Introduction
1 OS & Computer Architecture Modern OS Functionality (brief review) Architecture Basics Hardware Support for OS Features.
What do operating systems do? manage processes manage memory and computer resources provide security features execute user programs make solving user.
Operating Systems CSE 411 CPU Management Oct Lecture 13 Instructor: Bhuvan Urgaonkar.
Microkernels, virtualization, exokernels Tutorial 1 – CSC469.
CS 153 Design of Operating Systems Spring 2015 Final Review.
Fall 2000M.B. Ibáñez Lecture 01 Introduction What is an Operating System? The Evolution of Operating Systems Course Outline.
CSE 451: Operating Systems Section 10 Project 3 wrap-up, final exam review.
Course Introduction Andy Wang COP 5611 Advanced Operating Systems.
OPERATING SYSTEMS Goals of the course Definitions of operating systems Operating system goals What is not an operating system Computer architecture O/S.
CS 346 – Chapter 1 Operating system – definition Responsibilities What we find in computer systems Review of –Instruction execution –Compile – link – load.
Operating Systems CSE 411 Multi-processor Operating Systems Multi-processor Operating Systems Dec Lecture 30 Instructor: Bhuvan Urgaonkar.
CE Operating Systems Lecture 3 Overview of OS functions and structure.
Computers Operating System Essentials. Operating Systems PROGRAM HARDWARE OPERATING SYSTEM.
Ihr Logo Operating Systems Internals & Design Principles Fifth Edition William Stallings Chapter 2 (Part II) Operating System Overview.
Operating System 2 Overview. OPERATING SYSTEM OBJECTIVES AND FUNCTIONS.
LINUX System : Lecture 7 Bong-Soo Sohn Lecture notes acknowledgement : The design of UNIX Operating System.
OSes: 3. OS Structs 1 Operating Systems v Objectives –summarise OSes from several perspectives Certificate Program in Software Development CSE-TC and CSIM,
1 Threads, SMP, and Microkernels Chapter Multithreading Operating system supports multiple threads of execution within a single process MS-DOS.
1: Operating Systems Overview 1 Jerry Breecher Fall, 2004 CLARK UNIVERSITY CS215 OPERATING SYSTEMS OVERVIEW.
Silberschatz, Galvin and Gagne  Operating System Concepts Operating Systems 1. Overview 2. Process Management 3. Storage Management 4. I/O Systems.
1 Rutgers UniversityCS 416: Operating Systems Final exam details December 22, pm-3pm. Venue: SEC 118. Tips: Spend time reading the questions before.
CSE 153 Design of Operating Systems Winter 2015 Midterm Review.
1/31/20161 Final Exam Dec 10. Monday. 4-7pm. Phelp 1160 Similar to midterm The exam is closed book. You can bring 2 page of notes (double sided) Nachos.
Concepts and Structures. Main difficulties with OS design synchronization ensure a program waiting for an I/O device receives the signal mutual exclusion.
Operating Systems CMPSC 473 Introduction and Overview August 24, Lecture 1 Instructor: Bhuvan Urgaonkar.
Major OS Components CS 416: Operating Systems Design, Spring 2001 Department of Computer Science Rutgers University
CSCI/CMPE 4334 Operating Systems Review: Exam 1 1.
Introduction to Operating Systems Concepts
Operating Systems CMPSC 473
Andy Wang COP 5611 Advanced Operating Systems
Course Introduction Dr. Eggen COP 6611 Advanced Operating Systems
Andy Wang COP 5611 Advanced Operating Systems
Lecture Note 0: Course Introduction
Introduction to Operating Systems
Chapter 1: Intro (excerpt)
CGS 3763 Operating Systems Concepts Spring 2013
Sarah Diesburg Operating Systems CS 3430
Operating Systems : Overview
Andy Wang Operating Systems COP 4610 / CGS 5675
Operating Systems : Overview
Operating Systems : Overview
LINUX System : Lecture 7 Lecture notes acknowledgement : The design of UNIX Operating System.
February 5, 2004 Adrienne Noble
Andy Wang COP 5611 Advanced Operating Systems
Operating Systems : Overview
Lecture Note 0: Course Introduction
CSE 153 Design of Operating Systems Winter 2019
Andy Wang COP 5611 Advanced Operating Systems
CSE 153 Design of Operating Systems Winter 2019
Sarah Diesburg Operating Systems COP 4610
Lecture Topics: 11/1 Hand back midterms
Andy Wang Operating Systems COP 4610 / CGS 5675
In Today’s Class.. General Kernel Responsibilities Kernel Organization
Presentation transcript:

Operating Systems CSE 411 Revision and final thoughts Revision and final thoughts Dec Lecture 33 Instructor: Bhuvan Urgaonkar

What did we learn? What is an operating system –A piece of software that runs on a computer (kernel) –Privileged mode Direct access to all hardware (device drivers) –Resource allocation Efficiency Fairness Contention resolution (e.g., synchronization) –Protection and isolation –(Easy/Agreed upon) interface to programmers Hides several hardware details and heterogeneity

What did we learn? Relation between hardware/architecture and operating system design –Impact of hardware characteristics on OS design Good example was disk management versus memory management –How hardware designers and architects assist OS designers Example - Atomic operations –What should the hardware do versus what should the OS do

What did we learn? Important architectural features –Interrupts: I/O devices, passage of time (scheduling) –Exceptions: Request services from OS Related OS abstraction –Signals: Inter-process communication, asynchronous handling of special events by OS and programs

What did we learn? Key abstractions provided by the OS –Process Related: threads, address space/virtual memory –File Related: device files

What did we learn? CPU management –Process, thread, kernel control paths User-level threads Kernels are usually multi-threaded –Scheduling Work conservation Proportional-share, reservation-based –Synchronization Mutual exclusion Semaphores –Deadlocks –Multi-processors have special scheduling and synchronization considerations

What did we learn? Memory management –Virtual memory Current memory technology: RAM Fragmentation: internal and external Paging Page table, TLB Page replacement Swap space: Extension of RAM –Caching and buffering in RAM for I/O devices –Sharing memory Memory mapping, CoW –Relation between memory manager and CPU scheduler Under memory pressure, VMM can become the de-facto CPU scheduler VMM needs to be designed with fairness and performance in mind

What did we learn? I/O management –Hardware characteristics, DMA –Close look at disk management Disk characteristics Disk scheduling –Multiple locations where scheduling occurs File systems –Data layout –Virtual File systems –Traditional file systems –Emerging file system: CAS Emerging systems based on Flash

Cross-cutting concerns/principles Caching and buffering Fairness and isolation Design for average/frequent case Virtualization –VMM, VFS, system calls, multi-programming Multiplexing of resources –Over-commitment of resources Accounting and monitoring

Research goals Traditional –Performance –Fairness –Isolation Increasingly important –Power –Manageability Self-* properties –Change management –Accountability and security

Operating systems topics we didn’t cover Traditional OS topics –OS externals (311) –System bootstrap –Synchronization: Monitors –Deadlocks: Banker’s algorithm –File systems: Log-structured file systems Multimedia systems Real-time systems Distributed systems (Chapters 16-18)

Some slides from a controversial talk by Rob Pike of UNIX fame Systems research is irrelevant!

Current research in operating systems

What do we make of this? Debatable and controversial arguments I would like to believe that the new OS papers graph doesn’t indicate the death of OS research –Research has moved on to other aspects, taken newer forms –Similar phenomenon are seen in other fields –Can you give any examples? I feel the focus and scope of OS research has changed –More on distributed systems, embedded systems –Issues other than performance

Where do we go from here/ what’s happening now? Sensors and embedded devices Highly distributed systems –P2P networks, grids Mobile computing –Ubiquitous computing Virtual machines –Multiple operating systems on a single computer! Data centers –Green computing

Final exam 2 hour Open-notes, open-book Easier than the mid-terms Do the final quiz carefully –Still not up, but will be sometime tomorrow Only topics covered in lectures Tentative structure –8 Short questions (2-3 sentences each): 40% –3 longer design/essay questions: 60%, one each on: CPU scheduling/synchronization Memory management Disk management / file systems

Thank You! Special thanks to Arjun and Yuan