Presentation is loading. Please wait.

Presentation is loading. Please wait.

System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention, Avoidance, and Detection Recovering from Deadlock Combined Approach.

Similar presentations


Presentation on theme: "System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention, Avoidance, and Detection Recovering from Deadlock Combined Approach."— Presentation transcript:

1 System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention, Avoidance, and Detection Recovering from Deadlock Combined Approach to Deadlock Handling

2  A set of blocked processes each: ◦ holding and waiting to acquire a resource held by another process in the set.  Example ◦ System has 2 tape drives. ◦ P1 and P2 each hold one tape drive and each needs another one.

3  Example: ◦ semaphores Q and S, initialized to 1 P0 P1 wait(S);wait(Q); wait(Q);wait(S); … … signal(S);signal(Q); signal(Q)signal(S);

4  Traffic only in one direction.  Resource: each section of a bridge.  If deadlocked: can be resolved if one car backs up (preempt resources and rollback).  Several cars may have to be backed up if a deadlock occurs.  Starvation is possible.

5

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

7  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. Deadlock may arise if 4 conditions hold simultaneously:

8 3. No preemption: ◦ a resource can be released only voluntarily by the process holding it, after that process has completed its task. 4. Circular wait: ∃ a set {P 0, P 1, …, P n } of waiting processes s.t.: ◦ 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.

9  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

10  Process:  Resource Type with 4 instances:  Pi requests instance of Rj  Pi is holding an instance of Rj PiPi RjRj PiPi RjRj

11

12  If graph contains no cycles  no deadlock.  If graph contains a cycle  ◦ if only one instance per resource type, then deadlock. ◦ if several instances per resource type, possibility of deadlock.

13

14

15 1. Ensure that the system will never enter a deadlock state. 2. Allow the system to enter a deadlock state and then recover. 3. Ignore the problem and pretend that deadlocks never occur in the system; ◦ Approach used by most operating systems, including UNIX and Windows.

16 Restrain the ways request can be made, such that one of the 4 conditions (from earlier) cannot happen: ➊ Mutual Exclusion (mutex) ◦ do not require mutex for sharable resources  (potential problems?); ◦ must hold for nonsharable resources.

17 ➋ Hold and Wait ◦ whenever a process requests a resource, it does not hold any other resources. Can be done by requiring either: 1.must request and be allocated all its resources before it begins execution, or 2.allow requests only when the process has none. ◦ low resource utilization; starvation possible.

18 ➌ No Preemption ◦ Must release all currently held resources if process requests another resource that cannot be immediately allocated to it. ◦ 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.

19 ➍ Circular Wait ◦ impose a total ordering of all resource types, and require that each process requests resources in an increasing order of enumeration. i.e. F(DVD Drive) = 1 F(disk drive) = 5 F(printer) = 12 If you have a resource, can only request resources with larger numbers. If you need something “smaller”, you have to release first.

20

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

22  Dynamically examines the resource- allocation state to ensure that there can never be a circular-wait condition.  Resource-allocation state is defined as: ◦ the number of available and allocated resources, and the maximum demands of the processes.

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

24  Sequence is safe if: ◦ for each P i, the resources that P i can still request can be satisfied by: currently available resources + resources held by all P j, with j<i.

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

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

27

28  Claim edge (dashed line) P i  R j means: ◦ process P j may request resource R j.  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.

29

30

31  Multiple instances.  Each process must a priori claim maximum use. (just like above)  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  n = # of processes  m = # of resources types.  Available: ◦ Vector of length m. ◦ if available[j] = k  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.

33  Allocation: ◦ n x m matrix. ◦ if Allocation[i,j] = k  P i has k instances of R j.  Need: ◦ n x m matrix. ◦ if Need[i,j] = k  P i may need k more instances of R j. Need [i,j] = Max[i,j] – Allocation [i,j].

34 ➊ Work, Finish: vectors of length m and n, respectively. ◦ Initialize:  Work = Available  Finish [i] = false; ∀i ➋ Find an i such that both: ◦ (a) Finish [i] = false ◦ (b) Need[i]  Work ◦ If no such i exists, go to step ➍ ➌ Work = Work + Allocation[i] Finish[i] = true go to step ➋ ➍ If Finish [i] == true for all i, then the system is in a safe state.

35  Request i = request vector for process P i.  Request i [j] = k  P i wants k instances of resource type R j. ➊ if Request i  Need i go to step 2.  else raise error condition (exceeded maximum claim) ➋ if Request i  Available, go to step 3. ◦ else P i must wait; (resources unavailable)

36 ➌ Pretend to allocate requested resources to Pi by modifying the state as follows:  Available = Available - Request i ;  Allocation i = Allocation i + Request i ;  Need i = Need i – Request i  Then run safety algorithm:  if safe  the resources are allocated to Pi.  if unsafe  Pi must wait, and the old resource-allocation state is restored

37  5 processes P 0 through P 4  3 resource types: A (10 instances), B (5 instances), and C (7 instances).

38 Snapshot at time T 0 : AllocationMax Available Need A B C A B C A B CA B C P0 0 1 0 7 5 3 3 3 27 4 3 P1 2 0 0 3 2 2 1 2 2 P2 3 0 2 9 0 26 0 0 P3 2 1 1 2 2 20 1 1 P4 0 0 2 4 3 3 4 3 1 Need = Max – Allocation

39  The system is in a safe state since the sequence: satisfies the safety criteria.  (Is there another safe sequence?)

40 AllocationNeedAvailable A B CA B CA B C P00 1 0 7 4 3 2 3 1 P13 0 21 0 2 P23 0 1 6 0 0 P32 1 1 0 1 1 P40 0 2 4 3 1 Can request for (1,0,2) by P1 be granted? Can request for (3,3,0) by P4 be granted? Can request for (0,2,0) by P0 be granted?

41  Allow system to enter deadlock state  Detection algorithm  Recovery scheme

42  Maintain wait-for graph ◦ Nodes are processes. ◦ P i  P j means 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.

43

44  Available: ◦ A vector of length m indicates the # of available resources of each type.  Allocation: ◦ n x m matrix that defines the # of resources of each type currently allocated to each process.

45  Request: ◦ n x m matrix for the current request of each process.  Request [i,j] = k,  P i is requesting k more instances of resource type. R j.

46  Work, Finish: vectors of length m and n, respectively  ➊ Initialize: ◦ (a) Work = Available ◦ (b) for (i = 1,2, …, n) if Allocation i  0 Finish[i] = false else Finish[i] = true  ➋ Find an index i such that both: ◦ (a)Finish[i] == false ◦ (b)Request i  Work ◦ if no such i exists, goto ➍.

47  ➌ Work = Work + Allocation i Finish[i] = true go to ➋.  ➍ if Finish[i] == false, for some i, then the system is in a deadlock state. if Finish[i] == false, then Pi is deadlocked Algorithm requires O(m x n 2) operations to detect deadlocks.

48  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 30 0 0 P 3 2 1 1 1 0 0 P 4 0 0 2 0 0 2 Sequence will result in Finish[i] = true, ∀ i.

49  P 2 requests an additional instance of type C. RequestAvailableA B C P 0 0 0 00 0 0 P 1 2 0 1 P 2 0 0 1 P 3 1 0 0 P 4 0 0 2  State of system? ◦ 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.

50  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 invoked arbitrarily, there may be many cycles in the resource graph: ◦ which of the many deadlocked processes “caused” deadlock?

51  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. ◦ 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?

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

53  Combine the three basic approaches ◦ prevention ◦ avoidance ◦ detection  allowing the use of the optimal approach for each of resources in the system.

54  Partition resources into hierarchically ordered classes.  Use most appropriate technique for handling deadlocks within each class.


Download ppt "System Model Deadlock Characterization Methods for Handling Deadlocks Deadlock Prevention, Avoidance, and Detection Recovering from Deadlock Combined Approach."

Similar presentations


Ads by Google