1 Chapter 7: Deadlock. 2 The Deadlock Problem System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention Deadlock Avoidance.

Slides:



Advertisements
Similar presentations
Chapter 7: Deadlocks.
Advertisements

Chapter 7: Deadlocks.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition Chapter 7: Deadlocks.
7.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts with Java – 8 th Edition Chapter 7: Deadlocks.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Lecture 12: Deadlocks (Chapter 7)
Silberschatz, Galvin and Gagne ©2013 Operating System Concepts – 9 th Edition Chapter 7: Deadlocks.
Lecture 7: Deadlocks, Deadlock Risk Management. Lecture 7 / Page 2AE4B33OSS Silberschatz, Galvin and Gagne ©2005 Contents The Concept of Deadlock Resource-Allocation.
Deadlocks CS 3100 Deadlocks1. The Deadlock Problem A set of blocked processes each holding a resource and waiting to acquire a resource held by another.
Silberschatz, Galvin and Gagne  Operating System Concepts Chapter 8: Deadlocks System Model Deadlock Characterization Methods for Handling Deadlocks.
Chapter 7. Deadlocks.
Chapter 7: Deadlocks. 7.2 Chapter Objectives To develop a description of deadlocks, which prevent sets of concurrent processes from completing their tasks.
Chapter 8: Deadlocks System Model Deadlock Characterization
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts - 7 th Edition, Feb 14, 2005 Chapter 7: Deadlocks The Deadlock.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 7: Deadlocks.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 7: Deadlocks.
Deadlocks Gordon College Stephen Brinton. Deadlock Overview The Deadlock Problem System Model Deadlock Characterization Methods for Handling Deadlocks.
1 School of Computing Science Simon Fraser University CMPT 300: Operating Systems I Ch 7: Deadlock Dr. Mohamed Hefeeda.
What we will cover…  The Deadlock Problem  System Model  Deadlock Characterization  Methods for Handling Deadlocks  Deadlock Prevention  Deadlock.
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts - 7 th Edition, Feb 14, 2005 Objectives Understand the Deadlock.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition Deadlocks.
Silberschatz, Galvin and Gagne  Operating System Concepts Chapter 8: Deadlocks System Model Deadlock Characterization Methods for Handling Deadlocks.
Chapter 7: Deadlocks Adapted to COP4610 by Robert van Engelen.
System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention, Avoidance, and Detection Recovering from Deadlock Combined Approach.
Silberschatz, Galvin and Gagne ©2013 Operating System Concepts – 9 th Edition Chapter 7: Deadlocks.
Chapter 7 Deadlocks. 7.2 Modified By Dr. Khaled Wassif Operating System Concepts – 7 th Edition Silberschatz, Galvin and Gagne ©2005 Chapter 7: Deadlocks.
Cosc 4740 Chapter 6, Part 4 Deadlocks. The Deadlock Problem A set of blocked processes each holding a resource and waiting to acquire a resource held.
Computer Architecture and Operating Systems CS 3230: Operating System Section Lecture OS-6 Deadlocks Department of Computer Science and Software Engineering.
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 AE4B33OSS Chapter 7: Deadlocks The Deadlock Problem System Model Deadlock Characterization.
CHAPTER 8: DEADLOCKS System Model Deadlock Characterization
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 7: Deadlocks The Deadlock Problem System Model Deadlock.
 The Deadlock Problem  System Model  Deadlock Characterization  Methods for Handling Deadlocks  Deadlock Prevention  Deadlock Avoidance  Deadlock.
Dr. Kalpakis CMSC 421, Operating Systems Deadlocks.
Operating System Concepts 7th Edition Abraham SilBerschatz Peter Baer Galvin Greg Gagne Prerequisite: CSE212.
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 7: Deadlocks System Model Deadlock Characterization Methods.
Lecture 12 Handling Deadlock – Prevention, avoidance and detection.
Mi-Jung Choi Dept. of Computer and Science Silberschatz, Galvin and Gagne ©2006 Operating System Principles Chapter 7: Deadlocks.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 7: Deadlocks.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Lecture 7 Operating Systems.
Operating Systems Unit VI Deadlocks and Protection Department of Computer Science Engineering and Information Technology.
Chapter 8 Deadlocks. Objective System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention Deadlock Avoidance Deadlock Detection.
Chapter 7: Deadlocks. 7.2CSCI 380 – Operating Systems Chapter 7: Deadlocks The Deadlock Problem System Model Deadlock Characterization Methods for Handling.
7.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition Chapter 7: Deadlocks The Deadlock Problem System Model Deadlock Characterization.
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 7: Deadlocks The Deadlock Problem System Model Deadlock.
CS307 Operating Systems Deadlocks Fan Wu Department of Computer Science and Engineering Shanghai Jiao Tong University Spring 2012.
國立台灣大學 資訊工程學系 Chapter 7: Deadlocks. 資工系網媒所 NEWS 實驗室 Chapter Objectives To develop a description of deadlocks, which prevent sets of concurrent processes.
Chap 7 Deadlocks. Chapter Objectives To develop a description of deadlocks, which prevent sets of concurrent processes from completing their tasks To.
1 CS.217 Operating System By Ajarn..Sutapart Sappajak,METC,MSIT Chapter 6 Deadlocks Slide 1 Chapter 6 Deadlocks.
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 7: Deadlocks The Deadlock Problem System Model Deadlock.
Silberschatz, Galvin and Gagne  Operating System Concepts Chapter 8: Deadlocks System Model Deadlock Characterization Methods for Handling Deadlocks.
Deadlocks Introduction to Operating Systems: Module 7.
7.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts with Java – 8 th Edition Chapter 7: Deadlocks.
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter Objectives To develop a description of deadlocks, which.
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 7: Deadlocks The Deadlock Problem System Model Deadlock.
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 7: Deadlocks The Deadlock Problem System Model Deadlock.
7.1 CSE Department MAITSandeep Tayal 7: Deadlocks System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention Deadlock Avoidance.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition Chapter 7: Deadlocks.
Chapter 7: Deadlocks. 7.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts - 7 th Edition, Feb 14, 2005 Chapter 7: Deadlocks The Deadlock.
CSE Operating System Principles Deadlocks. CSE – Operating System Principles2 Overview System Model Deadlock Characterization Methods for.
Chapter 7: Deadlocks. The Deadlock Problem System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention Deadlock Avoidance.
Silberschatz, Galvin and Gagne ©2013 Operating System Concepts – 9 th Edition Chapter 7: Deadlocks.
Chapter 7: Deadlocks.
Chapter 7: Deadlocks.
Chapter 7: Deadlocks.
G.Anuradha Ref:- Galvin
Chapter 7: Deadlocks.
Outline Deadlocks, dead lock prevention, avoidance.
Chapter 7: Deadlocks.
Chapter 7: Deadlocks.
Presentation transcript:

1 Chapter 7: Deadlock

2 The Deadlock Problem System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention Deadlock Avoidance Deadlock Detection Recovery from Deadlock

3 Chapter Objectives To develop a description of deadlocks, which prevent sets of concurrent processes from completing their tasks To present a number of different methods for preventing or avoiding deadlocks in a computer system

4 The Deadlock Problem Defn: A set of blocked processes each holding a resource and waiting to acquire a resource held by another process in the set Example: System has 2 disk drives P 1 and P 2 each hold one disk drive and each needs another one P 1 and P 2 each hold one disk drive and each needs another oneExample semaphores A and B, initialized to 1 semaphores A and B, initialized to 1 P 0 P 1 P 0 P 1 wait (A);wait(B) wait (B);wait(A)

5 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)

6 Bridge Crossing Example Several cars may have to be backed up if a deadlock occurs Starvation is possible Note – Most OSes do not prevent or deal with deadlocks

7 System Model Resource types R 1, R 2,..., R m Ex: CPU cycles, memory space, I/O devices Ex: CPU cycles, memory space, I/O devices Each resource type R i has W i instances. Each process utilizes a resource as follows: request request use use release release

8 Deadlock Characterization 1. Mutual exclusion: only one process at a time can use a resource 2. Hold and wait: a process holding at least one resource is waiting to acquire additional resources held by other processes 3. No preemption: a resource can be released only voluntarily by the process holding it, after that process has completed its task Deadlock can arise if four conditions hold simultaneously.

9 Deadlock Characterization 4. Circular wait: there exists a set {P 0, P 1, …, P 0 } 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, 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.

10 Resource-Allocation Graph V is partitioned into two types: P = {P 1, P 2, …, P n }, the set consisting of all the processes in the system 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 R = {R 1, R 2, …, R m }, the set consisting of all resource types in the system request edge – directed edge P i  R j assignment edge – directed edge R j  P i A set of vertices V and a set of edges E.

11 Resource-Allocation Graph (Cont.) Process Resource Type with 4 instances P i requests instance of R j P i is holding an instance of R j PiPi RjRj PiPi RjRj

12 Example of a Resource Allocation Graph

13 Resource Allocation Graph With A Deadlock

14 Graph With A Cycle But No Deadlock

15 Basic Facts If graph contains no cycles  no deadlock If graph contains a cycle  if only one instance per resource type, then deadlock if only one instance per resource type, then deadlock if several instances per resource type, possibility of deadlock if several instances per resource type, possibility of deadlock

16 Methods for Handling Deadlocks Ensure that the system will never enter a deadlock state Allow the system to enter a deadlock state and then recover Ignore the problem and pretend that deadlocks never occur in the system Used by most operating systems, including UNIX Used by most operating systems, including UNIX Occasionally restart system manually after deadlock drags system to a halt. Occasionally restart system manually after deadlock drags system to a halt.

17 Deadlock Prevention 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 Two possible protocols: Two possible protocols: 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 Low resource utilization; starvation possible Restrain the ways a request can be made

18 No Preemption – (one protocol) 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 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 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 Process will be restarted only when it can regain its old resources, as well as the new ones that it is requesting

No Preemption – (second protocol) If a process requests some resources, first a check is made and if resources are available, they are allocated. If a process requests some resources, first a check is made and if resources are available, they are allocated. If some resources are not available, check to see if these resources are allocated to some other process that is waiting for additional resources. If some resources are not available, check to see if these resources are allocated to some other process that is waiting for additional resources. If so, the desired resources are preempted and allocated. If resources are not either available nor held by a waiting process, the requesting process must wait If resources are not either available nor held by a waiting process, the requesting process must wait While waiting, some of its resources may be preempted by another processor. It can restart only after it obtains requested and lost resources. 19

Circular Wait – impose a total ordering of all resource types, and require that each process requests resources in an increasing order of enumeration Multiple resources of the same type must be requested at the same time. Multiple resources of the same type must be requested at the same time. Does not work if locks can be acquired dynamically. Does not work if locks can be acquired dynamically. See textbook for further details. See textbook for further details. 20

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

22 Safe State Note: A basic consideration when deciding which deadlock avoidance algorithm to use. When a process requests an available resource, system must decide if immediate allocation leaves the system in a safe state System is in a safe state if there exists a sequence of ALL the processes in the systems such that for each P i, the resources that P i can still request can be satisfied by currently available resources + resources held by all the P j, with j of ALL the processes in the systems such that for each P i, the resources that P i can still request can be satisfied by currently available resources + resources held by all the P j, with j < i.

23 That is: If P i resource needs are not immediately available, then P i can wait until all P j have finished 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 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 When P i terminates, P i +1 can obtain its needed resources, and so on

24 Basic Facts If a system is in safe state  no deadlocks If a system is in unsafe state  possibility of deadlock Avoidance  ensure that a system will never enter an unsafe state.

25 Safe, Unsafe, Deadlock State

26 Avoidance algorithms Single instance of a resource type Use a resource-allocation graph Use a resource-allocation graph Multiple instances of a resource type Use the banker’s algorithm Use the banker’s algorithm

27 Resource-Allocation Graph Scheme A claim edge P i  R j indicates that process P i may request resource R j ; represented by a dashed line A claim edge converts to a request edge when a process requests a resource A request edge converts to an assignment edge when the resource is allocated to the process When a resource is released by a process, assignment edge reconverts to a claim edge Resources must be claimed a priori in the system

28 Resource-Allocation Graph

29 Unsafe State In Resource- Allocation Graph

30 Resource-Allocation Graph Algorithm Suppose that process P i requests a resource R j The request can be granted only if converting the request edge to an assignment edge does not result in the formation of a cycle in the resource allocation graph

31 Banker’s Algorithm Multiple instances 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

32 Data Structures for the Banker’s Algorithm 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] Let n = number of processes, and m = number of resources types.

33 Safety Algorithm 1.Let Work and Finish be vectors of length m and n, respectively. Initialize: Work = Available Finish [i] = false for i = 0, 1, …, n- 1 2.Find an 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

34 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 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 ==>> ==>>

35 3.Pretend to allocate requested resources to P i by modifying the state as follows: Available = Available – Request; Allocation i = Allocation i + Request i ; Need i = Need i – Request i ; l If safe  the resources are allocated to Pi l If unsafe  Pi must wait, and the old resource-allocation state is restored

36 Example of Banker’s Algorithm 5 processes P 0 through P 4 ; 3 resource types: A (10 instances), B (5 instances), and C (7 instances) 3 resource types: A (10 instances), B (5 instances), and C (7 instances) Snapshot at time T 0 : Allocation Max Available A B C A B C A B C A B C A B C A B C P P P P P P P P P

37 Example (Cont.) The content of the matrix Need is defined to be Max – Allocation Need A B C A B C P P P P P P P P P P The system is in a safe state since the sequence satisfies safety criteria

38 Example: P 1 Request (1,0,2) 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 A B C A B C A B C P P P P P Executing safety algorithm shows that sequence satisfies safety requirement

39 Can request for (3,3,0) by P 4 be granted? Can request for (0,2,0) by P 0 be granted?

40 Deadlock Detection Allow system to enter deadlock state Detection algorithm Recovery scheme

41 Single Instance of Each Resource Type Maintain wait-for graph Nodes are processes Nodes are processes P i  P j if P i is waiting for P j P i  P j if P i is waiting for P j Periodically invoke an algorithm that searches for a cycle in the graph. If there is a cycle, there exists a deadlock 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

42 Resource-Allocation Graph and Wait-for Graph a) Resource-Allocation Graph b) Corresponding wait-for graph

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

44 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

45 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 The algorithm requires an order of O(m x n 2) operations to detect whether the system is in a deadlocked state

46 Example of Detection Algorithm Five processes P 0 through P 4 ; three resource types: (7 instances), B (2 instances), and C (6 instances) Snapshot at time T 0 : Allocation RequestAvailable A B C A B C A B C A B C A B C A B C P P P P P Sequence will result in Finish[i] = true for all i

47 Example (Cont.) P 2 requests an additional instance of type C Request A B C P P P P P P P

48 State of system? Can reclaim resources held by process P 0, but insufficient resources to fulfill other processes; requests 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 Deadlock exists, consisting of processes P 1, P 2, P 3, and P 4

49 Detection-Algorithm Usage When, and how often, to invoke depends on: How often a deadlock is likely to occur? How often a deadlock is likely to occur? How many processes will need to be rolled back? How many processes will need to be rolled back? one for each disjoint cycle If the 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

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

51 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

52 End of Chapter 7