Chapter 8: Deadlocks. Operating System Concepts with Java

Similar documents
Chapter 8: Deadlocks. The Deadlock Problem

Chapter 7: Deadlocks. Operating System Concepts 8 th Edition,

Chapter 7: Deadlocks. Chapter 7: Deadlocks. The Deadlock Problem. Chapter Objectives. System Model. Bridge Crossing Example

Chapter 7: Deadlocks

Chapter 8: Deadlocks

Chapter 8: Deadlocks. The Deadlock Problem. System Model. Bridge Crossing Example. Resource-Allocation Graph. Deadlock Characterization

Chapter 7 : 7: Deadlocks Silberschatz, Galvin and Gagne 2009 Operating System Concepts 8th Edition, Chapter 7: Deadlocks

The Deadlock Problem

Chapter 7: Deadlocks

Module 7: Deadlocks. The Deadlock Problem. Bridge Crossing Example. System Model

Chapter 7: Deadlocks

Chapter 7: Deadlocks. Operating System Concepts with Java 8 th Edition

Module 7: Deadlocks. The Deadlock Problem

Module 7: Deadlocks. System Model. Deadlock Characterization. Methods for Handling Deadlocks. Deadlock Prevention. Deadlock Avoidance

Chapter 7: Deadlocks. Operating System Concepts 9 th Edition

Deadlocks. Deadlock Overview

Chapter 7: Deadlocks. Operating System Concepts 8 th Edition,! Silberschatz, Galvin and Gagne 2009!

Chapter 7: Deadlocks

UNIT-5 Q1. What is deadlock problem? Explain the system model of deadlock.

Deadlock Prevention. Restrain the ways request can be made. Mutual Exclusion not required for sharable resources; must hold for nonsharable resources.

Deadlock. Concepts to discuss. A System Model. Deadlock Characterization. Deadlock: Dining-Philosophers Example. Deadlock: Bridge Crossing Example

CMSC 412. Announcements

Principles of Operating Systems

CS307: Operating Systems

CSE Opera+ng System Principles

Chapter 7: Deadlocks. Operating System Concepts 8 th Edition,

Chapter 7: Deadlocks. Operating System Concepts 9 th Edition

CS307 Operating Systems Deadlocks

Deadlocks. Bridge Crossing Example. The Problem of Deadlock. Deadlock Characterization. Resource-Allocation Graph. System Model

The Deadlock Problem (1)

Chapter 8: Deadlocks. The Deadlock Problem

The Deadlock Problem. Chapter 8: Deadlocks. Bridge Crossing Example. System Model. Deadlock Characterization. Resource-Allocation Graph

Lecture 7 Deadlocks (chapter 7)

CHAPTER 7: DEADLOCKS. By I-Chen Lin Textbook: Operating System Concepts 9th Ed.

Deadlock Risk Management

System Model. Types of resources Reusable Resources Consumable Resources

Principles of Operating Systems

Chapter 7: Deadlocks. Operating System Concepts 9 th Edition

Deadlocks. Jinkyu Jeong Computer Systems Laboratory Sungkyunkwan University

Chapter 7: Deadlocks. Operating System Concepts 9 th Edition

Bridge Crossing Example

Chapter 7: Deadlocks. Operating System Concepts 9th Edition DM510-14

Roadmap. Safe State. Deadlock Avoidance. Basic Facts. Safe, Unsafe, Deadlock State. Tevfik Koşar. CSC Operating Systems Spring 2007

Chapter 7: Deadlocks. Operating System Concepts 9 th Edition! Silberschatz, Galvin and Gagne 2013!

Chapter 8: Deadlocks. The Deadlock Problem

ICS Principles of Operating Systems. Lectures Set 5- Deadlocks Prof. Nalini Venkatasubramanian

Deadlocks. Operating System Concepts - 7 th Edition, Feb 14, 2005

The Slide does not contain all the information and cannot be treated as a study material for Operating System. Please refer the text book for exams.

Deadlocks. Minsoo Ryu. Real-Time Computing and Communications Lab. Hanyang University.

Silberschatz, Galvin and Gagne 2013! CPU cycles, memory space, I/O devices! " Silberschatz, Galvin and Gagne 2013!

Deadlocks. Prepared By: Kaushik Vaghani

Roadmap. Deadlock Prevention. Deadlock Prevention (Cont.) Deadlock Detection. Exercise. Tevfik Koşar. CSE 421/521 - Operating Systems Fall 2012

Operating Systems 2015 Spring by Euiseong Seo DEAD LOCK

Chapter 7: Deadlocks. Operating System Concepts 8th Edition, modified by Stewart Weiss

COP 4610: Introduction to Operating Systems (Spring 2016) Chapter 7 Deadlocks. Zhi Wang Florida State University

Chapter 7: Deadlocks. Operating System Concepts 9 th Edition

The Deadlock Problem

The Deadlock Problem. A set of blocked processes each holding a resource and waiting to acquire a resource held by another process in the set.

The Deadlock Problem

CS420: Operating Systems. Deadlocks & Deadlock Prevention

CSC Operating Systems Fall Lecture - XII Deadlocks - III. Tevfik Ko!ar. Louisiana State University. October 6 th, 2009

Module 6: Deadlocks. Reading: Chapter 7

CHAPTER 7 - DEADLOCKS

Chapter 7: Deadlocks. Chapter 7: Deadlocks. System Model. Chapter Objectives

Deadlocks. Dr. Yingwu Zhu

Chapter 7: Deadlocks CS370 Operating Systems

Unit-03 Deadlock and Memory Management Unit-03/Lecture-01

Chapter 7: Deadlocks. Chapter 7: Deadlocks. Deadlock Example. Chapter Objectives

Chapter 7: Deadlocks

Deadlock Risk Management

Deadlock. Operating Systems. Autumn CS4023

Chapter 8: Deadlocks. Bridge Crossing Example. The Deadlock Problem

Operating Systems. Designed and Presented by Dr. Ayman Elshenawy Elsefy

CS370 Operating Systems

Potential Deadlock Example

CS370 Operating Systems

COMP 3713 Operating Systems Slides Part 3. Jim Diamond CAR 409 Jodrey School of Computer Science Acadia University

Roadmap. Tevfik Koşar. CSE 421/521 - Operating Systems Fall Lecture - XI Deadlocks - II. University at Buffalo. Deadlocks. October 6 th, 2011

Deadlocks. The Deadlock Problem. Bridge Crossing Example. Topics

When Deadlock Happens

Roadmap. Tevfik Ko!ar. CSC Operating Systems Spring Lecture - X Deadlocks - II. Louisiana State University. Deadlocks

Deadlock. Chapter Objectives

OPERATING SYSTEMS. Prescribed Text Book. Operating System Principles, Seventh Edition. Abraham Silberschatz, Peter Baer Galvin and Greg Gagne

Chapter - 4. Deadlocks Important Questions

Deadlock. A Bit More on Synchronization. The Deadlock Problem. Deadlock Characterization. Operating Systems 2/7/2005. CSC 256/456 - Spring

Maximum CPU utilization obtained with multiprogramming. CPU I/O Burst Cycle Process execution consists of a cycle of CPU execution and I/O wait

TDDB68 + TDDD82. Lecture: Deadlocks

CS370 Operating Systems

CS370 Operating Systems

Deadlocks. Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University

Fall 2015 COMP Operating Systems. Lab 06

University of Babylon / College of Information Technology / Network Department. Operating System / Dr. Mahdi S. Almhanna & Dr. Rafah M.

Resource Allocation and Deadlock Handling

UNIT-3 DEADLOCKS DEADLOCKS

Operating Systems. Deadlock. Lecture 7 Michael O Boyle

CSC 539: Operating Systems Structure and Design. Spring 2005

Chapter 7: Deadlocks. Operating System Concepts 9 th Edition

CS370 Operating Systems

OPERATING SYSTEMS. Deadlocks

The deadlock problem

Transcription:

Chapter 8: Deadlocks System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention Deadlock Avoidance Deadlock Detection Recovery from Deadlock Combined Approach to Deadlock Handling 8.1 Silberschatz, Galvin and Gagne 2003

The Deadlock Problem A set of blocked processes each holding a resource and waiting to acquire a resource held by another process in the set. Example 1 System has 2 tape drives. P 1 and P 2 each hold one tape drive and each needs another one. Example 2 semaphores A and B, initialized to 1 P 0 P 1 wait (A); wait (B); wait(b) wait(a) 8.2 Silberschatz, Galvin and Gagne 2003

Bridge Crossing Example Traffic only in one direction. Each section of a bridge can be viewed as a resource. If a deadlock occurs, it can be resolved if one car backs up (preempt resources and rollback). why is this hard to do? Several cars may have to be backed up if a deadlock occurs. Starvation is possible. 8.3 Silberschatz, Galvin and Gagne 2003

System Model Resource types R 1, R 2,..., R m CPU cycles, memory space, I/O devices Each resource type R i has W i instances. W = 1, 2, 3,... Each process utilizes a resource as follows: request use release 8.4 Silberschatz, Galvin and Gagne 2003

Deadlock Characterization Deadlock can arise if four conditions hold simultaneously. Mutual exclusion: only one process at a time can use a resource. Hold and wait: a process holding at least one resource is waiting to acquire additional resources held by other processes. No preemption: a resource can be released only voluntarily by the process holding it, after that process has completed its task. Circular wait: there exists a set {P 0, P 1,,P n } of waiting processes such that P 0 is waiting for a resource that is held by P 1, P 1 is waiting for a resource that is held by P 2,, P n 1 is waiting for a resource that is held by P n, and P n is waiting for a resource that is held by P 0. 8.5 Silberschatz, Galvin and Gagne 2003

Resource-Allocation Graph A set of vertices V and a set of edges E. V is partitioned into two types: P = {P 1, P 2,, P n }, the set consisting of all the processes in the system. R = {R 1, R 2,, R m }, the set consisting of all resource types in the system. request edge directed edge P 1 R j assignment edge directed edge R j P i 8.6 Silberschatz, Galvin and Gagne 2003

Process Resource-Allocation Graph (Cont.) Resource Type with 4 instances P i requests instance of R j P i R j P i is holding an instance of R j P i R j 8.7 Silberschatz, Galvin and Gagne 2003

Example of a Resource Allocation Graph 8.8 Silberschatz, Galvin and Gagne 2003

Resource Allocation Graph With A Deadlock 8.9 Silberschatz, Galvin and Gagne 2003

Resource Allocation Graph With A Cycle But No Deadlock 8.10 Silberschatz, Galvin and Gagne 2003

Basic Facts If graph contains no cycles, then no deadlock. If graph contains a cycle, then if only one instance per resource type, then deadlock. if several instances per resource type, possibility of deadlock. 8.11 Silberschatz, Galvin and Gagne 2003

Methods for Handling Deadlocks Ensure that the system will never enter a deadlock state. How? Allow the system to enter a deadlock state and then recover. How? Ignore the problem and pretend that deadlocks never occur in the system; used by most operating systems, including UNIX. well...not really. what if P(deadlock) =.000000001? 8.12 Silberschatz, Galvin and Gagne 2003

Deadlock Prevention Restrain the ways request can be made. Mutual Exclusion not required for sharable resources; must hold for nonsharable resources. Hold and Wait must guarantee that whenever a process requests a resource, it does not hold any other resources. Require process to request and be allocated all its resources before it begins execution, or allow process to request resources only when the process has none. Low resource utilization; starvation possible. 8.13 Silberschatz, Galvin and Gagne 2003

Deadlock Prevention (Cont.) No Preemption If a process that is holding some resources requests another resource that cannot be immediately allocated to it, then all resources currently being held are released. Preempted resources are added to the list of resources for which the process is waiting. Process will be restarted only when it can regain its old resources, as well as the new ones that it is requesting. Circular Wait impose a total ordering of all resource types, and require that each process requests resources in an increasing order of enumeration. 8.14 Silberschatz, Galvin and Gagne 2003

Deadlock Avoidance Requires that the system has some additional a priori information available. Simplest and most useful model requires that each process declare the maximum number of resources of each type that it may need. why is this difficult? The deadlock-avoidance algorithm dynamically examines the resource-allocation state to ensure that there can never be a circular-wait condition. why is this difficult? Resource-allocation state is defined by the number of available and allocated resources, and the maximum demands of the processes. why is this difficult? 8.15 Silberschatz, Galvin and Gagne 2003

Safe State When a process requests an available resource, system must decide if immediate allocation leaves the system in a safe state. System is in safe state if there exists a safe sequence of all processes. Sequence <P1, P2,, Pn> is safe if for each Pi, the resources that Pi can still request can be satisfied by currently available resources + resources held by all the Pj, with j< i. If P i resource needs are not immediately available, then P i can wait until all P j have finished. When P j is finished, P i can obtain needed resources, execute, return allocated resources, and terminate. When P i terminates, P i+1 can obtain its needed resources, and so on. 8.16 Silberschatz, Galvin and Gagne 2003

Basic Facts If a system is in safe state then no deadlocks. but only if we know the state If a system is in unsafe state then possibility of deadlock. Avoidance: ensure that a system will never enter an unsafe state. 8.17 Silberschatz, Galvin and Gagne 2003

Safe, Unsafe, Deadlock State 8.18 Silberschatz, Galvin and Gagne 2003

Resource-Allocation Graph Algorithm Claim edge P i R j indicated that process P j may request resource R j ; represented by a dashed line. Claim edge converts to request edge when a process requests a resource. When a resource is released by a process, assignment edge reconverts to a claim edge. Resources must be claimed a priori in the system. 8.19 Silberschatz, Galvin and Gagne 2003

Resource-Allocation Graph For Deadlock Avoidance 8.20 Silberschatz, Galvin and Gagne 2003

Unsafe State In Resource-Allocation Graph 8.21 Silberschatz, Galvin and Gagne 2003

Banker s Algorithm Multiple instances of each resource type. Each process must a priori claim maximum use. When a process requests a resource it may have to wait. When a process gets all its resources it must return them in a finite amount of time. 8.22 Silberschatz, Galvin and Gagne 2003

Data Structures for the Banker s Algorithm Let n = number of processes, and m = number of resources types. Available: Vector of length m. If available [j] = k, there are k instances of resource type R j available. Max: n x m matrix. If Max [i,j] = k, then process P i may request at most k instances of resource type R j. Allocation: n x m matrix. If Allocation[i,j] = k then P i is currently allocated k instances of R j. Need: n x m matrix. If Need[i,j] = k, then P i may need k more instances of R j to complete its task. Need [i,j] = Max[i,j] Allocation [i,j]. 8.23 Silberschatz, Galvin and Gagne 2003

Safety Algorithm 1. Let Work and Finish be vectors of length m and n, respectively. Initialize: Work = Available Finish [i] = false for i = 1,, n. 2. Find and i such that both: (a) Finish [i] = false (b) Need i Work If no such i exists, go to step 4. 3. Work = Work + Allocation i Finish[i] = true go to step 2. 4. If Finish [i] == true for all i, then the system is in a safe state. 8.24 Silberschatz, Galvin and Gagne 2003

Resource-Request Algorithm for Process P i Request = request vector for process P i. If Request i [j] = k then process P i wants k instances of resource type R j. 1. If Request i Need i go to step 2. Otherwise, raise error condition, since process has exceeded its maximum claim. 2. If Request i Available, go to step 3. Otherwise P i must wait, since resources are not available. 3. Pretend to allocate requested resources to P i by modifying the state as follows: Available = Available = Request i ; Allocation i = Allocation i + Request i ; Need i = Need i Request i;; 1. If safe, the resources are allocated to P i. 2. If unsafe, P i must wait, and the old resource-allocation state is restored 8.25 Silberschatz, Galvin and Gagne 2003

Example of Banker s Algorithm 5 processes P 0 through P 4 3 resource types A (10 instances), B (5instances, and C (7 instances). Snapshot at time T 0 : Allocation Max Available A B C A B C A B C P 0 0 1 0 7 5 3 3 3 2 P 1 2 0 0 3 2 2 P 2 3 0 2 9 0 2 P 3 2 1 1 2 2 2 P 4 0 0 2 4 3 3 8.26 Silberschatz, Galvin and Gagne 2003

Example (Cont.) The content of the matrix. Need is defined to be Max Allocation. Need A B C P 0 7 4 3 P 1 1 2 2 P 2 6 0 0 P 3 0 1 1 P 4 4 3 1 The system is in a safe state since the sequence < P 1, P 3, P 4, P 2, P 0 > satisfies safety criteria. 8.27 Silberschatz, Galvin and Gagne 2003

Example P 1 Request (1,0,2) (Cont.) Check that Request Available (that is, (1,0,2) (3,3,2) true. Allocation Need Available A B C A B C A B C P 0 0 1 0 7 4 3 2 3 0 P 1 3 0 2 0 2 0 P 2 3 0 1 6 0 0 P 3 2 1 1 0 1 1 P 4 0 0 2 4 3 1 Executing safety algorithm shows that sequence <P1, P3, P4, P0, P2> satisfies safety requirement. Can request for (3,3,0) by P4 be granted? Can request for (0,2,0) by P0 be granted? 8.28 Silberschatz, Galvin and Gagne 2003

Deadlock Detection Allow system to enter deadlock state Detection algorithm Recovery scheme 8.29 Silberschatz, Galvin and Gagne 2003

Single Instance of Each Resource Type Maintain wait-for graph Nodes are processes. P i P j if P i is waiting for P j. Periodically invoke an algorithm that searches for a cycle in the graph. An algorithm to detect a cycle in a graph requires an order of n 2 operations, where n is the number of vertices in the graph. 8.30 Silberschatz, Galvin and Gagne 2003

Resource-Allocation Graph and Wait-for Graph Resource-Allocation Graph Corresponding wait-for graph 8.31 Silberschatz, Galvin and Gagne 2003

Several Instances of a Resource Type Available: A vector of length m indicates the number of available resources of each type. Allocation: An n x m matrix defines the number of resources of each type currently allocated to each process. Request: An n x m matrix indicates the current request of each process. If Request [i j ] = k, then process P i is requesting k more instances of resource type. R j. 8.32 Silberschatz, Galvin and Gagne 2003

Detection Algorithm 1. Let Work and Finish be vectors of length m and n, respectively Initialize: (a) Work = Available (b) For i = 1,2,, n, if Allocation i 0, then Finish[i] = false;otherwise, Finish[i] = true. 2. Find an index i such that both: (a) Finish[i] == false (b) Request i Work If no such i exists, go to step 4. 8.33 Silberschatz, Galvin and Gagne 2003

Detection Algorithm (Cont.) 3. Work = Work + Allocation i Finish[i] = true go to step 2. 4. If Finish[i] == false, for some i, 1 i n, then the system is in deadlock state. Moreover, if Finish[i] == false, then P i is deadlocked. Algorithm requires an order of O(m x n 2) operations to detect whether the system is in deadlocked state. 8.34 Silberschatz, Galvin and Gagne 2003

Example of Detection Algorithm Five processes P 0 through P 4 ; three resource types A (7 instances), B (2 instances), and C (6 instances). Snapshot at time T 0 : Allocation Request Available A B C A B C A B C P 0 0 1 0 0 0 0 0 0 0 P 1 2 0 0 2 0 2 P 2 3 0 3 0 0 0 P 3 2 1 1 1 0 0 P 4 0 0 2 0 0 2 Sequence <P 0, P 2, P 3, P 1, P 4 > will result in Finish[i] = true for all i. 8.35 Silberschatz, Galvin and Gagne 2003

Example (Cont.) P 2 requests an additional instance of type C. State of system? Request A B C P 0 0 0 0 P 1 2 0 1 P 2 0 0 1 P 3 1 0 0 P 4 0 0 2 Can reclaim resources held by process P 0, but insufficient resources to fulfill other processes; requests. Deadlock exists, consisting of processes P 1, P 2, P 3, and P 4. 8.36 Silberschatz, Galvin and Gagne 2003

Detection-Algorithm Usage When, and how often, to invoke depends on: How often a deadlock is likely to occur? How many processes will need to be rolled back? one for each disjoint cycle If detection algorithm is invoked arbitrarily, there may be many cycles in the resource graph and so we would not be able to tell which of the many deadlocked processes caused the deadlock. 8.37 Silberschatz, Galvin and Gagne 2003

Recovery from Deadlock: Process Termination Abort all deadlocked processes. why is this a bad idea? Abort one process at a time until the deadlock cycle is eliminated. In which order should we choose to abort? Priority of the process. How long process has computed, and how much longer to completion. Resources the process has used. Resources process needs to complete. How many processes will need to be terminated. Is process interactive or batch? 8.38 Silberschatz, Galvin and Gagne 2003

Recovery from Deadlock: Resource Preemption Selecting a victim minimize cost. Rollback return to some safe state, restart process for that state. Starvation same process may always be picked as victim, include number of rollback in cost factor. 8.39 Silberschatz, Galvin and Gagne 2003

Combined Approach to Deadlock Handling Combine the three basic approaches prevention avoidance detection allowing the use of the optimal approach for each of resources in the system. Partition resources into hierarchically ordered classes. Use most appropriate technique for handling deadlocks within each class. 8.40 Silberschatz, Galvin and Gagne 2003

Traffic Deadlock for Exercise 8.3 8.41 Silberschatz, Galvin and Gagne 2003

Classroom Discussion Pg 312, problem 8.12: Can a system detect that some of its processes are starving? If you answer yes, explain how it can. If you answer no, explain how the system can deal with the starvation problem. 8.42 Silberschatz, Galvin and Gagne 2003

Classroom Discussion Pg 312, problem 8.12: Can a system detect that some of its processes are starving? If you answer yes, explain how it can. If you answer no, explain how the system can deal with the starvation problem. define starvation waiting unreasonable amount of time T for a resource process predetermines T or, allocate resources based on longest waiting time allocate to starving processes first 8.43 Silberschatz, Galvin and Gagne 2003