1 / 32

Deadlocks

Deadlocks. Topics. - System Model - Deadlock characterization - Methods for handling deadlocks - Deadlock prevention,avoidance - Deadlock detection and recovery. The Deadlock Problem.

yvon
Download Presentation

Deadlocks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Deadlocks Topics - System Model - Deadlock characterization - Methods for handling deadlocks - Deadlock prevention,avoidance - Deadlock detection and recovery

  2. 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: System has two tape drives. Process P_1 and P_2 each holds one and needs the other tape. • - Example: P1: wait(B); wait(A); • P2: wait(A); wait(B);

  3. Bridge Crossing Example • - Traffic only in one direction • - Each direction of a bridge can be viewed as resource. • - If a deadlock occurs, it can be resolved if one car backs up (preempt and rollback) • - Backing up may be impossible • - Starvation is possible

  4. System Model • Resource types R1, R2, …, R_{m-1} • 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 and release

  5. Deadlock Characterization • Deadlock can arise if four conditions • hold simultaneously. • - Mutual Exclusion • - Hold and Wait • - No preemption • - Circular Wait

  6. Resource-Allocation Graph • A set of vertices V and edges E • V is partitioned into two types: -P={P1,P2,…,Pn}, the set consisting of all the processes in the system and R={R1,R2,…,Rm}, the set consisting of all resources in the system. • Request edge - directed edge from Pi to Rj • Assignment edge - directed edge from Rj • to Pi.

  7. Resource-Allocation Graph • Process • Resources type with 4 instances • Pi Requests an instance of Rj

  8. Example of a Graph with no cycle R3 R1 P2 P3 R2 P1 R4

  9. Example of a graph with a cycle P2 P1 R1 P3 R2 P4

  10. Basic Facts • - If a graph contains no cycle implies no deadlock • - If a graph contains a cycle • - if only one instance per resource type then there is dead lock • - If several instances per resource type possibility of dead lock.

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

  12. Deadlock prevention • - Restrain the ways resource requests are • made. • - Hold and wait - must guarantee that • whenever a process requests a resource, it does not hold any other resources - either request before a process begins execution or when the process has none • - Low resource utilization - starvation • possible.

  13. Deadlock prevention • No preemption - if a process requests a resource that cannot be allocated, all currently held resources are released. • Circular wait - imposes a total ordering of all resource types, and require that each process requests resources in an increasing order of enumeration.

  14. Deadlock Avoidance • Requires that the system a priori • information available maximum number • of resources needed. • Dead-lock avoidance algorithm • dynamically examines the resource- • allocation to ensure that there is no • circular wait. • Resource allocation state is defined by • the number of available and allocated • resources and the maximum demands.

  15. 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 a safe state if there exists a • safe sequence for all processes. • Sequence <P1,P2,…,Pn> is safe for each • Pi, if the requests of Pi- can still request • can be satisfied by currently available • resources and resources held by Pj with j • < I.

  16. Basic Facts • - If a system is in safe state implies no • deadlocks. • - If a system is in unsafe state implies • possibility of deadlock. • - Avoidance implies ensure that a system will never enter an unsafe state.

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

  18. Data Structures for the Banker’s Algorithm • N= number of processes, m= available • resources • Available- vector Available[j]=k means • that there are k instances of resource • types Rj. • Allocation -n x m matrix If Allocation[I,j]=k • means process Pi has been allocated k • units of resource type Rj.

  19. Data Structures for the Banker’s Algorithm (continued) • Need - n x m matrix. • If Need[I,j]=m means process Pi needs m • units of resource type Rj. • Need[I,j]=Max[I,j]-Allocation[I,j]

  20. Safety Algorithm • 1) Let Work and Finish be vectors of length m and n rsply: initialize Work=Available and Finish=false • 2) Find a I such that both Finish_I=false and Need_I<Work . If no such I exists go to step 4. • 3) Work=Work+Allocation_I; Finish=true; goto step 2. • 4) If Finish_I is true for all I, then the system is in a safe state.,

  21. Resource-Request Algorithm for Process P_i 1. If Request_I <= Need_I goto step 2. Otherwise error condition. 2. If Request_I <= Available, goto step 3. Otherwise,P_I must wait. 3. Pretend to allocate requested resource by modifying the state.Available=Available-Request_I; Allocation_i=Allocation_I+Request_I; Need_I=Need_I-Request_I; If Safe requests are allocated else P_I waits.

  22. Example • 5 processes P0 to P4; 3 Resource types A • (10 instances), B(5 instances) and C(7 • instances) • Snap slot at time T0 • Allocation Max Available • A B C A B C A B C • 0 1 0 7 5 3 3 3 2 • 2 0 0 3 2 2 • 3 0 2 9 0 2 • 2 1 1 2 2 2 • 0 0 2 4 3 3

  23. Example • P1 Requests (1,0,2) • Can a request of (3,3,0) of P4 be granted • Cana request (0,2,0) by P0 be granted.

  24. Deadlock Detection • Allow system to enter deadlock state. • Detection Algorithm • Recovery scheme

  25. Single Instance of Resource Type • Maintain wait-for graph (nodes are • processes, An edge Pi to Pj denotes that • Pi is waiting for Pj). • Periodically invoke an algorithm for • finding cycle.

  26. Multiple Instances of Resource Type • Data Structures Available, Allocation and • Request as for Banker’s Algorithm • Algorithm: • 1) Let Work and Finish be vectors of length m and n resply. Initialize: Work=Available. If Allocation_I <>) then Finish_I=false else Finish_I=true; • 2) Find an index I such that Finish[I]=false and Request[I]<=Work - if no such I exists goto 4.

  27. Multiple Instances of Resource Type • 3) Work=Work+Allocation Finsih[I]=true; • goto step 2. • 4) If Finish[I=false for some I, then the • system is in a deadlock state. Moreover, • if Finish[I]=false, then Pi is deadlocked.

  28. Example • 5 Processes three resource types A(&),B(2) and C (6). • Snapshot at t0. • Allocation Request Available • A B C A B C A B C • 0 1 0 0 0 0 0 0 0 • 2 0 0 2 0 2 • 3 0 3 0 0 0 • 2 1 1 1 0 0 • 0 0 2 0 0 2

  29. Detection Algorithm Usage • When and how to invoke depends on how • often a deadlock is likely to occur and • how many processes will be needed to • rollback • We also have to know which processes • caused deadlock

  30. Recovery from Deadlock • Abort all processes • Abort one process at a time until the • deadlock cycle is eliminated. • Which process to abort - priority, how • long computation has been done, • resources, interactive or batch

  31. Recovery from Deadlock • Selecting a victim - minimize cost • Rollback - return to safe state. • Starvation

  32. Combined Approach to Deadlock Handling • Combine the three basic approaches - • Prevention, Avoidance and detection • Partition the resources into hierarchically • ordered classes • Use most appropriate technique for • handling deadlocks within each class.

More Related