OPERATING SYSTEMS NOTES FROM GITAM WEBSITE

Operating Systems

Home

Chapter 1: Operating SystemsChapter 2: Computer-System StructuresChapter 3: Operating-System Structures Chapter 4: ProcessesChapter5: CPU Scheduling Chapter 6: Process SynchronizationChapter 7: DeadlocksChapter 8: Memory ManagementChapter 9: File-System InterfaceChapter 10: File System ImplementationChapter 11: ProtectionChapter 12 : Security Module 1 : The Linux SystemModule 2: Windows 2000

Chapter 1: Operating Systems

1.1 Operating System1.2 Mainframe Systems1.3 Desktop Systems1.4 Distributed Systems & Real Time systems

Operating System

A program that acts as an intermediary between a user of a computer and the computer hardware.Operating system goals:Provide environment in which user can execute programs and make solving user problems easier.Make the computer system convenient to use. Use the computer hardware in an efficient manner. Computer System Components 1. Hardware – provides basic computing resources (CPU, memory, I/ O devices). 2. Operating system – controls and coordinates the use of the hardware among the various application programs for the various users.

3. Applications programs – define the ways in which the system resources are used to solve the computing problems of the users (compilers, database systems, video games, business programs). 4. Users (people, machines, other computers).

Abstract View of System Components

Operating System DefinitionsResource allocator – manages and allocates resources.Control program – controls the execution of userPrograms and operations of I/ O devices .Kernel – the one program running at all times (all else being application programs).

1.2 Mainframe Systems

Reduce setup time by batching similar jobs .Automatic job sequencing – automatically transfers control from one job to another. First rudimentary operating system. Resident monitor. initial control in monitor .control transfers to job .when job completes control transfers pack to monitor Memory Layout for a Simple Batch System

Multi-programmed Batch Systems

Several jobs are kept in main memory at the same time, and the CPU is multiplexed among them.

OS Features Needed for Multiprogramming I/ O routine supplied by the system.

Memory management – the system must allocate the memory to several jobs.

CPU scheduling – the system must choose among several jobs ready to run.

Allocation of devices.

Time- Sharing Systems– Interactive Computing

The CPU is multiplexed among several jobs that are kept in memory and on disk

(the CPU is allocated to a job only if the job is in memory).

A job swapped in and out of memory to the disk.

On- line communication between the user and the system is provided;

when the operating system finishes the execution of one command, it seeks the next “control statement” from the user’s keyboard.

On- line system must be available for users to access data and code.

1.3 Desktop Systems

Personal computers – computer system dedicated to a single user.

I/ O devices – keyboards, mice, display screens, small printers.

User convenience and responsiveness.

Can adopt technology developed for larger operating system’ often individuals have sole use of computer and do not need advanced CPU utilization of protection features. May run several different types of operating systems (Windows, Mac OS, UNIX, Linux) Parallel Systems. Multiprocessor systems with more than on CPU in close communication.

Tightly coupled system – processors share memory and a clock;

communication usually takes place through the shared memory.

Advantages of parallel system:

Increased throughput

Economical

Increased reliability

graceful degradation

fail- soft systems

Symmetric multiprocessing (SMP)

Each processor runs and identical copy of the operating system.

Many processes can run at once without performance deterioration.

Most modern operating systems support SMP Asymmetric multiprocessing

Each processor is assigned a specific task; master processor schedules and allocated work to slave processors.More common in extremely large systems

Symmetric Multiprocessing Architecture

1.4 Distributed Systems

Distribute the computation among several physical processors.

Loosely coupled system – each processor has its own local memory;Processors communicate with one another through various

communications lines, such as high- speed buses or telephone lines.

Advantages of distributed systems.

Resources Sharing

Computation speed up – load sharing

Reliability

Communications

Requires networking infrastructure.

Local area networks (LAN) or Wide area networks (WAN) May be either client- server or peer- to- peer systems.

General Structure of Client- Server

Clustered Systems

Clustering allows two or more systems to share storage.

Provides high reliability.

Asymmetric clustering: one server runs the application while other servers standby.

Symmetric clustering: all N hosts are running the application.

Real- Time Systems

Often used as a control device in a dedicated application such as controlling scientific experiments, medical imaging systems, industrial control systems, and some display systems.

Well- defined fixed- time constraints.

Real- Time systems may be either hard or soft real- time.

Hard real- time:

Secondary storage limited or absent, data stored in short term memory, or read- only memory (ROM)

Conflicts with time- sharing systems, not supported by general- purpose operating systems.

Soft real- time

Limited utility in industrial control of robotics

Useful in applications (multimedia, virtual reality) requiring advanced operating- system features.

Handheld Systems

Personal Digital Assistants (PDAs) Cellular telephones Issues:

Limited memory

Slow processors

Small display screens.

Migration of Operating- System Concepts and Features

Computing Environments

Traditional computing

Web- Based Computing

Embedded Computing

Computer-System Architecture

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. 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.

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 Time Line For a Single Process Doing Output

I/O Structure

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.

Two I/O Methods

Synchronous Asynchronous

Device-Status Table

Direct Memory Access Structure 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.

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.

Moving-Head Disk Mechanism

Storage Hierarchy

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.

Storage-Device Hierarchy

Caching

Use of high-speed memory to hold recently-accessed data.

Requires a cache management policy.

Caching introduces another level in storage hierarchy.

This requires data that is simultaneously stored in more than one level to be consistent.

Migration of A From Disk to Register

BACK

Hardware Protection

Dual-Mode Operation

I/O Protection

Memory Protection

CPU Protection

Dual-Mode Operation

Sharing system resources requires operating system to ensure that an incorrect program cannot cause

other programs to execute incorrectly. Provide hardware support to differentiate between at least two

modes of operations.

1. User mode – execution done on behalf of a user.

2. Monitor mode (also kernel mode or system mode) – execution done on behalf of operating system.

Mode bit added to computer hardware to indicate the current mode: monitor (0) or user (1).

When an interrupt or fault occurs hardware switches to monitor mode.

Privileged instructions can be issued only in monitor mode.

I/O Protection

All I/O instructions are privileged instructions. Must ensure that a user program could never gain control

of the computer in monitor mode (I.e., a user program that, as part of its execution, stores a new address in the interrupt vector).

Use of A System Call to Perform I/O

Memory Protection

Must provide memory protection at least for the interrupt vector and the interrupt service routines. In order to have memory protection, add two registers that determine the range of legal

addresses a program may access:

Base register – holds the smallest legal physical memory address.

Limit register – contains the size of the range Memory outside the defined range is protected.

Use of A Base and Limit Register

Hardware Address Protection

Hardware Protection

When executing in monitor mode, the operating system has unrestricted access to both monitor and user’s memory. The load instructions for the base and limit registers are privileged instructions.

CPU Protection

1.Timer – interrupts computer after specified period to ensure operating system maintains control.

2.Timer is decremented every clock tick.

3.When timer reaches the value 0, an interrupt occurs.

Timer commonly used to implement time sharing.

Time also used to compute the current time.

Load-timer is a privileged instruction.

Network Structure

Local Area Networks (LAN)

Wide Area Networks (WAN)

Local Area Network Structure

Wide Area Network Structure

BACK

3.1 Common System Components

Process Management

Main Memory Management

File Management

I/O System Management

Secondary Management

Networking

Protection System

Command-Interpreter System

Process Management

A process is a program in execution. A process needs certain resources, including CPU time, memory,

files, and I/O devices, to accomplish its task.

The operating system is responsible for the following activities in connection with process management.

1. Process creation and deletion.

2. Process suspension and resumption.

3. Provision of mechanisms for:

4. Process synchronization

5. Process communication

Main-Memory Management

1. Memory is a large array of words or bytes, each with its own address. It is a repository of quickly

accessible data shared by the CPU and I/O devices.

2. Main memory is a volatile storage device. It loses its contents in the case of system failure.

The operating system is responsible for the following activities in connections with memory management:

1. Keep track of which parts of memory are currently being used and by whom.

2. Decide which processes to load when memory space

becomes available.

3. Allocate and de allocate memory space as needed.

File Management

A file is a collection of related information defined by its creator. Commonly, files represent programs

(both source and object forms) and data.

The operating system is responsible for the following activities in connections with file management:

1. File creation and deletion.

2. Directory creation and deletion.

3. Support of primitives for manipulating files and directories.

4. Mapping files onto secondary storage.

5. File backup on stable (nonvolatile) storage media.

I/O System Management

The I/O system consists of:

1. A buffer-caching system

2. A general device-driver interface

3. Drivers for specific hardware devices

Secondary-Storage Management

Since main memory (primary storage) is volatile and too small to accommodate all data and programs

permanently, the computer system must provide secondary storage to back up main memory. Most modern computer systems use disks as the principle on-line storage medium, for both programs and data.

The operating system is responsible for the following activities in connection with disk management:

1. Free space management

2. Storage allocation

3. Disk scheduling

Networking (Distributed Systems)

A distributed system is a collection processors that do not share memory or a clock. Each processor has its own local memory. The processors in the system are connected through a communication network.

Communication takes place using a protocol.

A distributed system provides user access to various system resources.

Access to a shared resource allows:

1. Computation speed-up

2. Increased data availability

3. Enhanced reliability

Protection System

Protection refers to a mechanism for controlling access by programs, processes, or users to both system and user resources.

The protection mechanism must:

1. distinguish between authorized and unauthorized usage.

2. specify the controls to be imposed.

3. Provide a means of enforcement.

Command-Interpreter System

Many commands are given to the operating system by control statements which deal with:

1. Process creation and management

2. I/O handling

3. Secondary-storage management

4. Main-memory management

5. File-system access

6. Protection

7. Networking

The program that reads and interprets control statements is called variously:

1. Command-line interpreter

2. Shell (in UNIX)

Its function is to get and execute the next command statement.

BACK

Operating System Services

Program execution – system capability to load a program into memory and to run it.

I/O operations – since user programs cannot execute I/O operations directly, the operating system must provide some means to perform I/O.

File-system manipulation – program capability to read, write, create, and delete files.

Communications – exchange of information between processes executing either on the same computer or on different systems tied together by a network. Implemented via shared memory or message passing.

Error detection – ensure correct computing by detecting errors in the CPU and memory hardware, in I/O

devices, or in user programs.

Additional Operating System Functions

Additional functions exist not for helping the user, but rather for

ensuring efficient system operations.

1. Resource allocation – allocating resources to multiple users or multiple jobs running at the same time.

2. Accounting – keep track of and record which users use how much and what kinds of computer

resources for account billing or for accumulating usage statistics.

3. Protection – ensuring that all access to system resources is controlled.

System Calls

System calls provide the interface between a running program and the operating system.

1. Generally available as assembly-language instructions.

2. Languages defined to replace assembly language for systems programming allow system calls

to be made directly (e.g., C, C++)

Three general methods are used to pass parameters between a running program and the operating system.

1. Pass parameters in registers.

2. Store the parameters in a table in memory, and the table address is passed as a parameter in a register.

3. Push (store) the parameters onto the stack by the program, and pop off the stack by operating system.

Passing of Parameters As A Table

Types of System Calls

1. Process control

2. File management

3. Device management

4. Information maintenance

5. Communications

MS-DOS Execution

At System Start-up Running a Program

UNIX Running Multiple Programs

Communication Models

Msg Passing Shared Memory

Communication may take place using either message passing or shared memory.

BACK

System Programs

System programs provide a convenient environment for program development and execution.

They can be divided into:

1. File manipulation

2. Status information

3. File modification

4. Programming language support

5. Program loading and execution

6. Communications

7. Application programs

Most users’ view of the operation system is defined by system programs, not the actual system calls.

MS-DOS System Structure

MS-DOS – written to provide the most functionality in the least space

1. not divided into modules

2.Although MS-DOS has some structure, its interfaces and levels of functionality are not well separated

MS-DOS Layer Structure

UNIX System Structure

UNIX – limited by hardware functionality, the original

UNIX operating system had limited structuring. The UNIX

OS consists of two separable parts.

1. Systems programs

2. The kernel

3. Consists of everything below the system-call interface and above the physical hardware

4. Provides the file system, CPU scheduling, memory management, and other operating-system functions;

a large number of functions for one level.

UNIX System Structure

Silberschatz, Galvin and Gagne 2002 3.25 Operating System Concepts

Layered Approach

The operating system is divided into a number of layers (levels), each built on top of lower layers. The bottom

layer (layer 0), is the hardware; the highest (layer N) is the user interface. With modularity, layers are selected

such that each uses functions (operations) and services of only lower-level layers.

An Operating System Layer

Microkernel System Structure

Moves as much from the kernel into “user” space.

Communication takes place between user modules using message passing.

Benefits:

easier to extend a microkernel

easier to port the operating system to new architectures more reliable (less code is running in kernel mode)

more secure

Windows NT Client-Server Structure

BACK

Virtual Machines

A virtual machine takes the layered approach to its logical conclusion. It treats hardware and the operating system kernel as though they were all hardware. A virtual machine provides an interface identical to the underlying bare hardware. The operating system creates the illusion

of multiple processes, each executing on its own processor with its own (virtual) memory.

The resources of the physical computer are shared to create

the virtual machines.

1. CPU scheduling can create the appearance that users have their own processor.

2. Spooling and a file system can provide virtual card readers and virtual line printers.

3. A normal user time-sharing terminal serves as the virtual machine operator’s console.

System Models

Non-virtual Machine Virtual Machine

Advantages/Disadvantages of Virtual Machines

The virtual-machine concept provides complete protection of system resources since each virtual machine is isolated from all other virtual machines. This isolation, however, permits no direct sharing of resources. A virtual-machine system is a perfect vehicle for operating-systems research and development. System development is done on the virtual machine, instead of on a physical machine and so does not disrupt normal system operation. The virtual machine concept is difficult to implement due to the effort required to provide an exact duplicate to the underlying machine.

Java Virtual Machine

Compiled Java programs are platform-neutral byte codes executed by a Java Virtual Machine (JVM). JVM consists of

1. class loader

2. class verifier

3. runtime interpreter

Just-In-Time (JIT) compilers increase performance

Java Virtual Machine

System Design Goals

User goals – operating system should be convenient to use, easy to learn, reliable, safe, and fast.

System goals – operating system should be easy to design, implement, and maintain, as well as flexible, reliable, error-free, and efficient.

Mechanisms and Policies

Mechanisms determine how to do something, policies decide what will be done.

The separation of policy from mechanism is a very important

principle, it allows maximum flexibility if policy decisions are to be changed later.

System Implementation

Traditionally written in assembly language, operating systems can now be written in higher-level languages.

Code written in a high-level language:

1. can be written faster.

2. is more compact.

3. is easier to understand and debug.

An operating system is far easier to port (move to some other hardware) if it is written in a high-level language.

System Generation (SYS GEN)

Operating systems are designed to run on any of a class of machines; the system must be configured for each specific computer site. SYS GEN program obtains information concerning the specific configuration of the hardware system.

Booting – starting a computer by loading the kernel.

Bootstrap program – code stored in ROM that is able to locate the kernel, load it into memory, and start its execution.

BACK

Process Concept

An operating system executes a variety of programs:

1. Batch system – jobs

2. Time-shared systems – user programs or tasks

Textbook uses the terms job and process almost interchangeably.

Process – a program in execution; process execution must progress in sequential fashion.

A process includes:

1. program counter

2. stack

3. data section

Process State

As a process executes, it changes state

1. new: The process is being created.

2. running: Instructions are being executed.

3. waiting: The process is waiting for some event to occur.

4. ready: The process is waiting to be assigned to a process.

5. terminated: The process has finished execution.

Diagram of Process State

Process Control Block (PCB)

Information associated with each process.

Process state

Program counter

CPU registers

CPU scheduling information

Memory-management information

Accounting information

I/O status information

CPU Switch From Process to Process

BACK

Process Scheduling Queues

Job queue – set of all processes in the system.

Ready queue – set of all processes residing in main memory, ready and waiting to execute.

Device queues – set of processes waiting for an I/O device.

Process migration between the various queues.

Ready Queue And Various I/O Device Queues

Representation of Process Scheduling

Schedulers

Long-term scheduler (or job scheduler) – selects which processes should be brought into the ready queue.

Short-term scheduler (or CPU scheduler) – selects which process should be executed next and allocates CPU.

Addition of Medium Term Scheduling

Short-term scheduler is invoked very frequently (milliseconds) _ (must be fast).

Long-term scheduler is invoked very infrequently (seconds, minutes) _ (may be slow).

The long-term scheduler controls the degree of multiprogramming.

Processes can be described as either:

1. I/O- bound process – spends more time doing I/O than computations, many short CPU bursts.

2. CPU-bound process – spends more time doing computations; few very long CPU bursts.

Context Switch

When CPU switches to another process, the system must save the state of the old process and load the saved state for the new

process.

Context-switch time is overhead; the system does no useful work while switching.

Time dependent on hardware support.

BACK

Operations on Processes:

Process Creation

Parent process create children processes, which, in turn create other processes, forming a tree of processes.

Resource sharing

1. Parent and children share all resources.

2. Children share subset of parent’s resources.

3. Parent and child share no resources.

Execution

4. Parent and children execute concurrently.

5. Parent waits until children terminate.

Address space

6. Child duplicate of parent.

7. Child has a program loaded into it.

UNIX examples

1. fork system call creates new process

2. exec system call used after a fork to replace the process’ memory space with a new program.

Processes Tree on a UNIX System

Process Termination

Process executes last statement and asks the operating system to decide it (exit).

1. Output data from child to parent (via wait).

2. Process’ resources are de allocated by operating

system.

Parent may terminate execution of children processes (abort).

3. Child has exceeded allocated resources.

4. Task assigned to child is no longer required.

5. Parent is exiting.

6. Operating system does not allow child to continue if its parent terminates.

7. Cascading termination.

Cooperating Processes

Independent process cannot affect or be affected by the execution of another process.

Cooperating process can affect or be affected by the execution of another process Advantages of process cooperation

1. Information sharing

2. Computation speed-up

3. Modularity

4. Convenience

Producer-Consumer Problem

Paradigm for cooperating processes, producer process

produces information that is consumed by consumer process.

1. unbounded-buffer places no practical limit on the size of the buffer.

2. bounded-buffer assumes that there is a fixed buffer size.

Bounded-Buffer – Shared-Memory Solution

Shared data

#define BUFFER_ SIZE 10

Type def struct {

. . .

} item;

item buffer [BUFFER_ SIZE];

int in = 0;

int out = 0;

Solution is correct, but can only use BUFFER_SIZE-1 elements

Silberschatz, Galvin and Gagne 2002 4.22 Operating System Concepts

Bounded-Buffer – Producer Process

item next Produced;

while (1) {

while (((in + 1) % BUFFER_ SIZE) == out)

; /* do nothing */

buffer [in] = next Produced;

in = (in + 1) % BUFFER_ SIZE;

}

Bounded-Buffer – Consumer Process

item next Consumed;

while (1) {

while (in == out)

; /* do nothing */

next Consumed = buffer [out];

out = (out + 1) % BUFFER _SIZE;

}

BACK

Inter process Communication (IPC)

Mechanism for processes to communicate and to synchronize their actions.

Message system – processes communicate with each other without resorting to shared variables.

IPC facility provides two operations:

1. send (message) – message size fixed or variable

2. receive (message)

If P and Q wish to communicate, they need to: establish a communication link between them exchange messages via send/receive Implementation of communication link

1. physical (e.g., shared memory, hardware bus)

2. logical (e.g., logical properties)

Implementation Questions

How are links established?

Can a link be associated with more than two processes?

How many links can there be between every pair of communicating processes?

What is the capacity of a link?

Is the size of a message that the link can accommodate fixed or variable?

Is a link unidirectional or bi-directional?

Direct Communication

Processes must name each other explicitly:

1. send (P, message) – send a message to process P

2. receive (Q, message) – receive a message from process Q Properties of communication link

3. Links are established automatically.

4. A link is associated with exactly one pair of communicating processes.

5. Between each pair there exists exactly one link.

6. The link may be unidirectional, but is usually bi-directional.

Indirect Communication

Messages are directed and received from mailboxes (also referred to as ports).

1. Each mailbox has a unique id.

2. Processes can communicate only if they share a mailbox.

Properties of communication link

1. Link established only if processes share a common mailbox

2. A link may be associated with many processes.

Each pair of processes may share several communication links.

1. Link may be unidirectional or bi-directional.


Operations

1. create a new mailbox

2. send and receive messages through mailbox

3. destroy a mailbox

Primitives are defined as:

Send (A, message) – send a message to mailbox A

receive (A, message) – receive a message from mailbox A


Mailbox sharing

1. P1, P2, and P3 share mailbox A.

2. P1, sends; P2 and P3 receive.

Who gets the message?

Solutions

1. Allow a link to be associated with at most two processes.

2. Allow only one process at a time to execute a receive operation.

3. Allow the system to select arbitrarily the receiver. Sender is notified who the receiver was.

Synchronization

Message passing may be either blocking or non-blocking.

Blocking is considered synchronous

Non-blocking is considered asynchronous

send and receive primitives may be either blocking or non-blocking.

Buffering

Queue of messages attached to the link; implemented in one of three ways.

1. Zero capacity – 0 messages

Sender must wait for receiver (rendezvous).

2. Bounded capacity – finite length of n messages Sender must wait if link full.

3. Unbounded capacity – infinite length

Sender never waits.

BACK

Client-Server Communication

Sockets

Remote Procedure Calls

Remote Method Invocation (Java)

Sockets

1. A socket is defined as an endpoint for communication.

2. Concatenation of IP address and port

3. The socket 161.25.19.8:1625 refers to port 1625 on host 161.25.19.8

4. Communication consists between a pair of sockets.

Socket Communication

Remote Procedure Calls

Remote procedure call (RPC) abstracts procedure calls between processes on networked systems.

Stubs – client-side proxy for the actual procedure on the server.

The client-side stub locates the server and marshal's the parameters.

The server-side stub receives this message, unpacks the marshalled parameters, and performs the

procedure on the server.

Execution of RPC

Remote Method Invocation

Remote Method Invocation (RMI) is a Java mechanism similar to RPCs.

RMI allows a Java program on one machine to invoke a method on a remote object.

Marshalling Parameters

BACK

OPERATING SYSTEMS NOTES FROM GITAM WEBSITE

Documents

wide area networks

local area networks

remote method invocation

bound process spends

java virtual machine

communication takes place

unix system structure

system calls