Chapter 1: Introduction. Chapter 1: Introduction. Operating System Concepts, 7th Edition. Objectives



Similar documents
Lesson Objectives. To provide a grand tour of the major operating systems components To provide coverage of basic computer system organization

Lecture 1 Operating System Overview

Operating Systems Prof. Ashok K Agrawala

Computer-System Architecture

Chapter 1: Introduction. Operating System Concepts 9 th Edit9on

Operating Systems 4 th Class

Operating Systems Overview

Chapter 2: Computer-System Structures. Computer System Operation Storage Structure Storage Hierarchy Hardware Protection General System Architecture

Operating system Dr. Shroouq J.

1. Computer System Structure and Components

Introduction. System Calls

Chapter 1: Introduction. What is an Operating System?

Introduction to Operating Systems. Perspective of the Computer. System Software. Indiana University Chen Yu

Chapter 3: Operating-System Structures. System Components Operating System Services System Calls System Programs System Structure Virtual Machines

Chapter 3 Operating-System Structures

Introduction. What is an Operating System?

Overview of Operating Systems Instructor: Dr. Tongping Liu

Chapter 3: Operating-System Structures. Common System Components

Operating System Components

Operating System Tutorial

Contents. Chapter 1. Introduction

Types Of Operating Systems

OPERATING SYSTEMS STRUCTURES

Computer Science 4302 Operating Systems. Student Learning Outcomes

Review from last time. CS 537 Lecture 3 OS Structure. OS structure. What you should learn from this lecture

Principles of Operating Systems CS 446/646

Common Operating-System Components

CSC 2405: Computer Systems II

Chapter 1 Computer System Overview

Chapter 2: OS Overview

This tutorial will take you through step by step approach while learning Operating System concepts.

3 - Introduction to Operating Systems

Overview and History of Operating Systems

Chapter 2 Basic Structure of Computers. Jin-Fu Li Department of Electrical Engineering National Central University Jungli, Taiwan

CSE 120 Principles of Operating Systems. Modules, Interfaces, Structure

Management Challenge. Managing Hardware Assets. Central Processing Unit. What is a Computer System?

How To Understand And Understand An Operating System In C Programming

Chapter 11 I/O Management and Disk Scheduling

CHAPTER 15: Operating Systems: An Overview

Operating System Software

Chapter 6, The Operating System Machine Level

Chapter 2 System Structures

Computer Organization & Architecture Lecture #19

Chapter 5: System Software: Operating Systems and Utility Programs

Chapter 3. Operating Systems

Components of a Computer System

Operating System Structures

Operating System Concepts. Operating System 資 訊 工 程 學 系 袁 賢 銘 老 師

Operating Systems. Lecture 03. February 11, 2013

Operating Systems: Basic Concepts and History

Programming for GCSE Topic H: Operating Systems

Overview of MIS Professor Merrill Warkentin

EECS 678: Introduction to Operating Systems

Computers: Tools for an Information Age

Chapter 3: Operating Systems

CS161: Operating Systems

Processes and Non-Preemptive Scheduling. Otto J. Anshus

CHAPTER 7: The CPU and Memory

How To Understand The History Of An Operating System

Operating Systems PART -A

Client/Server Computing Distributed Processing, Client/Server, and Clusters

Kernel. What is an Operating System? Systems Software and Application Software. The core of an OS is called kernel, which. Module 9: Operating Systems

I/O Device and Drivers

TEST CHAPTERS 1 & 2 OPERATING SYSTEMS

Chapter 11: File System Implementation. Operating System Concepts with Java 8 th Edition

Operating Systems. Notice that, before you can run programs that you write in JavaScript, you need to jump through a few hoops first

Distributed Systems. REK s adaptation of Prof. Claypool s adaptation of Tanenbaum s Distributed Systems Chapter 1

Introduction Disks RAID Tertiary storage. Mass Storage. CMSC 412, University of Maryland. Guest lecturer: David Hovemeyer.

Multiprogramming. IT 3123 Hardware and Software Concepts. Program Dispatching. Multiprogramming. Program Dispatching. Program Dispatching

Chapter 12: Mass-Storage Systems

lesson 1 An Overview of the Computer System

Have both hardware and software. Want to hide the details from the programmer (user).

Chapter 12: Secondary-Storage Structure

COS 318: Operating Systems. I/O Device and Drivers. Input and Output. Definitions and General Method. Revisit Hardware

Operating System Overview. Otto J. Anshus

Chapter 16: Virtual Machines. Operating System Concepts 9 th Edition

CHAPTER 1: OPERATING SYSTEM FUNDAMENTALS

I/O Management. General Computer Architecture. Goals for I/O. Levels of I/O. Naming. I/O Management. COMP755 Advanced Operating Systems 1

File System & Device Drive. Overview of Mass Storage Structure. Moving head Disk Mechanism. HDD Pictures 11/13/2014. CS341: Operating System

Learning Objectives. Chapter 1: Networking with Microsoft Windows 2000 Server. Basic Network Concepts. Learning Objectives (continued)

Fall Lecture 1. Operating Systems: Configuration & Use CIS345. Introduction to Operating Systems. Mostafa Z. Ali. mzali@just.edu.

Input / Output and I/O Strategies

Operating Systems OBJECTIVES 7.1 DEFINITION. Chapter 7. Note:

Software design (Cont.)

Objectives. Chapter 2: Operating-System Structures. Operating System Services (Cont.) Operating System Services. Operating System Services (Cont.

COS 318: Operating Systems. Virtual Machine Monitors

Multi-core architectures. Jernej Barbic , Spring 2007 May 3, 2007

International Engineering Journal For Research & Development

Operating Systems Overview As we have learned in working model of a computer we require a software system to control all the equipment that are

Storage. The text highlighted in green in these slides contain external hyperlinks. 1 / 14

Chap-02, Hardware and Software. Hardware Model

OS Concepts and structure

Computer Systems Structure Input/Output

Montgomery College Course Designator/Course Number: CS 110 Course Title: Computer Literacy

CS 377: Operating Systems. Outline. A review of what you ve learned, and how it applies to a real operating system. Lecture 25 - Linux Case Study

Outline: Operating Systems

Operating Systems Concepts: Chapter 7: Scheduling Strategies

Centralized Systems. A Centralized Computer System. Chapter 18: Database System Architectures

Chapter 1 FUNDAMENTALS OF OPERATING SYSTEM

Transcription:

Chapter 1: Introduction Chapter 1: Introduction 1.1 What Operating Systems Do 1.2 Computer-System Organization 1.3 Computer-System Architecture 1.4 Operating-System Structure 1.5 Operating-System Operations 1.6 Process Management 1.7 Memory Management 1.8 Storage Management 1.9 Protection and Security 1.10 Distributed Systems 1.11 Special-Purpose Systems 1.12 Computing Environments Operating System Concepts, 7th Edition Part I Overview Ch1. Introduction Ch2. Operating System Structures Part II Process Management Ch3. Processes Ch4. Threads Ch5. CPU Scheduling Ch6. Process Synchronization Ch7. Deadlocks Part III Memory Management Ch8. Memory Management Ch9. Virtual Memory Part IV Storage Management Ch10. File-System Interface Ch11. File-System Implementation Ch12. Mass-Storage Structure Ch13. I/O Systems 1.2 Part V Protection & Security Ch14. Protection Ch15. Security Part VI Distributed Systems Ch16. Distributed System Structures Ch17. Distributed File System Ch18. Distributed Coordination Part VII: Special Purpose Systems Ch19. Real-Time Systems Ch20. Multimedia Systems Part VIII Case Studies Ch21. The Linux Systems Ch22. Windows XP Ch23. Influential Operating Systems 1.3 Objectives To provide a grand tour of the major operating systems components To provide coverage of basic computer system organization 1.4

1.1 What is an Operating System? Four Components of a Computer System A program that acts as an intermediary between a user of a computer and the computer hardware. Operating system goals: Execute user programs and make solving user problems easier. Make the computer system convenient to use. Use the computer hardware in an efficient manner. 1.5 Computer System Structure 1.7 Operating System Definition Computer system can be divided into four components Hardware provides basic computing resources CPU, memory, I/O devices Operating system Controls and coordinates use of hardware among various applications and users Application programs define the ways in which the system resources are used to solve the computing problems of the users Word processors, compilers, web browsers, database systems, video games Users OS is a resource allocator Manages all resources Decides between conflicting requests for efficient and fair resource use OS is a control program Controls execution of programs to prevent errors and improper use of the computer People, machines, other computers 1.6 1.8

Operating System Definition (Cont.) No universally accepted definition Everything a vendor ships when you order an operating system is good approximation But varies wildly The one program running at all times on the computer is the kernel. Everything else is either a system program (ships with the operating system) or an application program 1.2 Computer System Organization 1.3 Computer System Architecture 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 1.9 Computer Startup 1.11 Computer-System Operation bootstrap program is loaded at power-up or reboot Typically stored in ROM or EEPROM, generally known as firmware Initializates all aspects of system Loads operating system kernel and starts execution I/O devices and the CPU can execute concurrently. Each device controller is in charge of a particular device type. Each device controller has a local buffer. CPU moves data from/to main memory to/from local buffers I/O is from the device to local buffer of controller. Device controller informs CPU that it has finished its operation by causing an interrupt. 1.10 1.12

Common Functions of Interrupts Interrupt Timeline Interrupt transfers control to the interrupt service routine generally, through the interrupt vector, which contains the addresses of all the service routines. Interrupt architecture must save the address of the interrupted instruction. Incoming interrupts are disabled while another interrupt is being processed to prevent a lost interrupt. A trap is a software-generated interrupt caused either by an error or a user request. An operating system is interrupt driven. 1.13 Interrupt Handling 1.15 I/O Structure The operating system preserves the state of the CPU by storing registers and the program counter. Determines which type of interrupt has occurred: polling vectored interrupt system Separate segments of code determine what action should be taken for each type of interrupt After I/O starts, control returns to user program only upon I/O completion. Wait instruction idles the CPU until the next interrupt Wait loop (contention for memory access). At most one I/O request is outstanding at a time, no simultaneous I/O processing. After I/O starts, control returns to user program without waiting for I/O completion. System call request to the operating system to allow user to wait for I/O completion. Device-status table contains entry for each I/O device indicating its type, address, and state. Operating system indexes into I/O device table to determine device status and to modify table entry to include interrupt. 1.14 1.16

Two I/O Methods Direct Memory Access Structure Synchronous Asynchronous Used for high-speed I/O devices able to transmit information at close to memory speeds. Device controller transfers blocks of data from buffer storage directly to main memory without CPU intervention. Only on interrupt is generated per block, rather than the one interrupt per byte. 1.17 Device-Status Table 1.19 Storage Structure Main memory only large storage media that the CPU can access directly. Secondary storage extension of main memory that provides large nonvolatile storage capacity. Magnetic disks rigid metal or glass platters covered with magnetic recording material Disk surface is logically divided into tracks, which are subdivided into sectors. The disk controller determines the logical interaction between the device and the computer. 1.18 1.20

Storage Hierarchy Caching Storage systems organized in hierarchy. Speed Cost Volatility Caching copying information into faster storage system; main memory can be viewed as a last cache for secondary storage. Important principle, performed at many levels in a computer (in hardware, operating system, software) Information in use copied from slower to faster storage temporarily Faster storage (cache) checked first to determine if information is there If it is, information used directly from the cache (fast) If not, data copied to cache and used there Cache smaller than storage being cached Cache management important design problem Cache size and replacement policy 1.21 Storage-Device Hierarchy 1.23 Performance of Various Levels of Storage Movement between levels of storage hierarchy can be explicit or implicit 1.22 1.24

Migration of Integer A from Disk to Register Memory/IRQ/IO Resource Management Multitasking environments must be careful to use most recent value, not matter where it is stored in the storage hierarchy Multiprocessor environment must provide cache coherency in hardware such that all CPUs have the most recent value in their cache Distributed environment situation even more complex Several copies of a datum can exist Various solutions covered in Chapter 17 控 制 台 系 統 硬 體 裝 置 管 理 員 檢 視 資 源 ( 依 類 型 ) 1.25 Interactions among CPU, memory and I/O 1.27 1.4 Operating System Structure inport/outport mov mem[], Rx interrupt DMA (Direct Memory Access) Multiprogramming needed for efficiency Single user cannot keep CPU and I/O devices busy at all times Multiprogramming organizes jobs (code and data) so CPU always has one to execute A subset of total jobs in system is kept in memory One job selected and run via job scheduling When it has to wait (for I/O for example), OS switches to another job Timesharing (multitasking) is logical extension in which CPU switches jobs so frequently that users can interact with each job while it is running, creating interactive computing Response time should be < 1 second Each user has at least one program executing in memory process If several jobs ready to run at the same time CPU scheduling If processes don t fit in memory, swapping moves them in and out to run Virtual memory allows execution of processes not completely in memory 1.26 1.28

Memory Layout for Multiprogrammed System Transition from User to Kernel Mode Timer to prevent infinite loop / process hogging resources Set interrupt after specific period Operating system decrements counter When counter zero generate an interrupt Set up before scheduling process to regain control or terminate program that exceeds allotted time 1.29 1.5 Operating-System Operations 1.31 1.6 Process Management Interrupt driven by hardware Software error or request creates exception or trap Division by zero, request for operating system service Other process problems include infinite loop, processes modifying each other or the operating system Dual-mode operation allows OS to protect itself and other system components User mode and kernel mode Mode bit provided by hardware Provides ability to distinguish when system is running user code or kernel code Some instructions designated as privileged, only executable in kernel mode System call changes mode to kernel, return from call resets it to user A process is a program in execution. It is a unit of work within the system. Program is a passive entity, process is an active entity. Process needs resources to accomplish its task CPU, memory, I/O, files Initialization data Process termination requires reclaim of any reusable resources Single-threaded process has one program counter specifying location of next instruction to execute Process executes instructions sequentially, one at a time, until completion Multi-threaded process has one program counter per thread Typically system has many processes, some user, some operating system running concurrently on one or more CPUs Concurrency by multiplexing the CPUs among the processes / threads 1.30 1.32

Process Management Activities 1.8 Storage Management The operating system is responsible for the following activities in connection with process management: Creating and deleting both user and system processes Suspending and resuming processes Providing mechanisms for process synchronization Providing mechanisms for process communication Providing mechanisms for deadlock handling OS provides uniform, logical view of information storage Abstracts physical properties to logical storage unit - file Each medium is controlled by device (i.e., disk drive, tape drive) Varying properties include access speed, capacity, datatransfer rate, access method (sequential or random) File-System management Files usually organized into directories Access control on most systems to determine who can access what OS activities include Creating and deleting files and directories Primitives to manipulate files and dirs Mapping files onto secondary storage Backup files onto stable (non-volatile) storage media 1.33 1.7 Memory Management 1.35 Mass-Storage Management All data in memory before and after processing All instructions in memory in order to execute Memory management determines what is in memory when Optimizing CPU utilization and computer response to users Memory management activities Keeping track of which parts of memory are currently being used and by whom Deciding which processes (or parts thereof) and data to move into and out of memory Allocating and deallocating memory space as needed Usually disks used to store data that does not fit in main memory or data that must be kept for a long period of time. Proper management is of central importance Entire speed of computer operation hinges on disk subsystem and its algorithms OS activities Free-space management Storage allocation Disk scheduling Some storage need not be fast Tertiary storage includes optical storage, magnetic tape Still must be managed Varies between WORM (write-once, read-many-times) and RW (readwrite) 1.34 1.36

I/O Subsystem 1.12 Computing Environments One purpose of OS is to hide peculiarities of hardware devices from the user I/O subsystem responsible for Memory management of I/O including buffering (storing data temporarily while it is being transferred), caching (storing parts of data in faster storage for performance), spooling (the overlapping of output of one job with input of other jobs) General device-driver interface Drivers for specific hardware devices Traditional computer Office environment PCs connected to a network, terminals attached to mainframe or minicomputers providing batch and timesharing Now portals allowing networked and remote systems access to same resources Home networks Used to be single system, then modems Now firewalled, networked 1.37 1.9 Protection and Security 1.39 Computing Environments (Cont.) Protection any mechanism for controlling access of processes or users to resources defined by the OS Security defense of the system against internal and external attacks Huge range, including denial-of-service, worms, viruses, identity theft, theft of service Systems generally first distinguish among users, to determine who can do what User identities (user IDs, security IDs) include name and associated number, one per user User ID then associated with all files, processes of that user to determine access control Group identifier (group ID) allows set of users to be defined and controls managed, then also associated with each process, file Privilege escalation allows user to change to effective ID with more rights Client-Server Computing Dumb terminals supplanted by smart PCs Many systems now servers, responding to requests generated by clients Compute-server provides an interface to client to request services (i.e. database) File-server provides interface for clients to store and retrieve files 1.38 1.40

Peer-to to-peer Computing Web-Based Computing Another model of distributed system P2P does not distinguish clients and servers Instead all nodes are considered peers May each act as client, server or both Node must join P2P network Registers its service with central lookup service on network, or Broadcast request for service and respond to requests for service via discovery protocol Examples include Napster and Gnutella Web has become ubiquitous PCs most prevalent devices More devices becoming networked to allow web access New category of devices to manage web traffic among similar servers: load balancers Use of operating systems like Windows 95, client-side, have evolved into Linux and Windows XP, which can be clients and servers 1.41 Shift of Computing Environment 1980~ Terminal-Mainframe (Super-computing) 1990~ Client-Server (Micro-computing /Personal Computer) 1.42 2000~ Peer-to-Peer (Macro-computing) RS-232 Dialup/10M Ethernet ADSL/100M + Ethernet Supercomputer Desktop Computer Embedded System Monitor CRT LCD VT100/DOS Windows 31/95 Linux/Windows 2K 1.43 End of Chapter 1 1.1 What Operating Systems Do 1.2 Computer-System Organization 1.3 Computer-System Architecture 1.4 Operating-System Structure 1.5 Operating-System Operations 1.6 Process Management 1.7 Memory Management 1.8 Storage Management 1.9 Protection and Security 1.10 Distributed Systems 1.11 Special-Purpose Systems 1.12 Computing Environments 1.44