Chapter 1: Introduction: Silberschatz, Galvin and Gagne ©2013 Operating System Concepts - 9 Edit9on

Chapter 1: Introduction
Operating System Concepts – 9th Edit9on Silberschatz, Galvin and Gagne ©2013
1. What an OS Do?
Operating System Concepts – 9th Edition 1.2 Silberschatz, Galvin and Gagne ©2013
What is an Operating System?
 A program that acts as an intermediary between a user of a

computer and the computer hardware
 A system software that manages computer hardware, software
resources, and provides common services for computer
programs
 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
Computer System Structure
 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
 People, machines, other computers
Four Components of a Computer System
What Operating Systems Do
User’s View:
Depends on the point of view
Users want convenience, ease of use and good performance
 Don’t care about resource utilization
But shared computer such as mainframe or minicomputer must
keep all users happy
Users of dedicate systems such as workstations have dedicated
resources but frequently use shared resources from servers
Handheld computers are resource poor, optimized for usability and
battery life
Some computers have little or no user interface, such as embedded
computers in devices and automobiles
Operating System Definition
System’s View:
 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
Operating System Definition (Cont.)
 No universally accepted definition

 “Everything a vendor ships when you order an operating
system” is a 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.
2. Computer System Organization
2.1 Computer System Operation
 Computer Startup:
 bootstrap program is loaded at power-up or reboot
 Typically stored in ROM or EPROM, generally known
as firmware
 Initializes all aspects of system
 Loads operating system kernel and starts execution
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
Computer-System Operation
 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
Common Functions of Interrupts
 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
 A trap or exception is a software-generated interrupt
caused either by an error or a user request
 An operating system is interrupt driven
Interrupt Handling
 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
Interrupt Timeline
Interrupt Timeline
2.2 Storage Structure
 Main memory – only large storage media that the CPU can access
directly
 Random access
 Typically volatile
 Secondary storage – extension of main memory that provides large
nonvolatile storage capacity
 Hard 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
 Solid-state disks – faster than hard disks, nonvolatile
 Various technologies
 Becoming more popular
Storage Hierarchy
 Storage systems organized in hierarchy

 Speed
 Cost
 Volatility
 Caching – copying information into faster storage system;
main memory can be viewed as a cache for secondary
storage
 Device Driver for each device controller to manage I/O
 Provides uniform interface between controller and
kernel
Storage-Device Hierarchy
Caching
 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
2.3 I/O Structure
 Synchronous vs asynchronous I/O
 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
Direct Memory Access Structure
 Direct memory access (DMA) is a method that allows

an input/output (I/O) device to send or receive data
directly to or from the main memory, bypassing the CPU
to speed up memory operations.
 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 one interrupt is generated per block, rather than
the one interrupt per byte
How a Modern Computer Works
A von Neumann architecture
3. Computer System Architecture
Computer-System Architecture
 Most systems use a single general-purpose processor

 Most systems have special-purpose processors as well
 Multiprocessors systems growing in use and importance
 Also known as parallel systems, tightly-coupled systems
 Advantages include:
1. Increased throughput
2. Economy of scale
3. Increased reliability – graceful degradation or fault tolerance
 Two types:
1. Asymmetric Multiprocessing – each processor is assigned a
specie task.
2. Symmetric Multiprocessing – each processor performs all tasks
Symmetric Multiprocessing Architecture
A Dual-Core Design
 Multi-chip and multicore
 Systems containing all chips
 Chassis containing multiple separate systems
Clustered Systems
 Like multiprocessor systems, but multiple systems working together

 Usually sharing storage via a storage-area network (SAN)
 Provides a high-availability service which survives failures
 Asymmetric clustering has one machine in hot-standby mode
 Symmetric clustering has multiple nodes running applications,
monitoring each other
 Some clusters are for high-performance computing (HPC)
 Applications must be written to use parallelization
 Some have distributed lock manager (DLM) to avoid conflicting
operations
Clustered Systems
4. Operating System Structure
Operating System Structure
 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
Memory Layout for Multiprogrammed System
5. Operating System Operations
Operating-System Operations
 Interrupt driven (hardware and software)
 Hardware interrupt by one of the devices
 Software interrupt (exception or trap):
 Software error (e.g., division by zero)
 Request for operating system service
 Other process problems include infinite loop, processes
modifying each other or the operating system
5.1 Dual mode operation
 We need to make sure that an error in a user program could hurt only that
program
 in multiprogramming environment one program can cause problems for
other programs or even for OS
 Without protection; Only one process at a time or suspected output always
10/30/21
5.1 Dual mode operation…
 Dual-mode operation allows OS to protect itself and other system
components
 privileged instructions
 It contains user mode (mode bit:1) and Kernel mode (mode bit:0)
 The operating system loaded user application

starts in user mode. Whenever a trap or interrupt
occurs, hardware switches to kernel mode.
10/30/21
10/30/21
#include<stdio.h>
Int main()
{
…
printf(“hellow world”);
…
}
User mode
Standard C library
Kernel mode
Write()
system
call
10/30/21
5.2 Timer
 Need to ensure that OS maintain control over the CPU
 To prevent the OS out of control by CPU
 Set interrupt after specific period (fixed or variable)
 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
10/30/21
Resource Management
6. Process Management
Process Management
 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
Process Management Activities
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
7. Memory Management
Memory Management
 To execute a program all (or part) of the instructions must be in

memory
 All (or part) of the data that is needed by the program must be in
memory.
 Memory management determines what is in memory and 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
8. Storage Management
Storage Management
OS activities include
 Creating and deleting files and directories
 Primitives to manipulate files and directories
 Mapping files onto secondary storage
 Backup files onto stable (non-volatile) storage media
Mass-Storage Management
 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
 OS activities
 Free-space management
 Storage allocation
 Disk scheduling

Chapter 1: Introduction: Silberschatz, Galvin and Gagne ©2013 Operating System Concepts - 9 Edit9on

Uploaded by

Copyright:

Available Formats

Chapter 1: Introduction: Silberschatz, Galvin and Gagne ©2013 Operating System Concepts - 9 Edit9on

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 1: Introduction: Silberschatz, Galvin and Gagne ©2013 Operating System Concepts - 9 Edit9on

Uploaded by

Copyright:

Available Formats

Chapter 1: Introduction

 A program that acts as an intermediary between a user of a

 No universally accepted definition

 I/O devices and the CPU can execute concurrently

 Interrupt transfers control to the interrupt service routine

 The operating system preserves the state of the CPU by

 Storage systems organized in hierarchy

 Important principle, performed at many levels in a computer

 Direct memory access (DMA) is a method that allows

A von Neumann architecture

 Most systems use a single general-purpose processor

 Like multiprocessor systems, but multiple systems working together

 Timesharing (multitasking) is logical extension in which CPU switches jobs

 The operating system loaded user application

The operating system is responsible for the following activities in

 To execute a program all (or part) of the instructions must be in

You might also like