Concurrency Deadlock and Starvation Chapter 6 1 Deadlock
- Slides: 52
Concurrency: Deadlock and Starvation Chapter 6 1
Deadlock • Permanent blocking of a set of processes that either compete for system resources or communicate with each other • No efficient solution • Involve conflicting needs for resources by two or more processes 2
3
4
Six different execution paths: 1. 2. 3. 4. 5. 6. Q acquires B and then A and then releases B and A. when P resumes execution, it will be able to acquire both resources. Q acquires B and then A. P executes and blocks on a request for A. Q releases B and A. When P resumes execution , it will be able to acquire both resources. Q acquires B and then P acquires A. Deadlock is inevitable, because as execution proceeds, Q will block on A and P will block on B. P acquires A and then Q acquires B. Deadlock is inevitable, because as execution proceeds, Q will block on A and P will block on B. P acquires A and then B. Q executes and blocks on a request for B. P releases A and B. When Q resumes execution, it will be able to acquire both resources. P acquires A and then B and then releases A and B. When Q resumes execution, it will be able to acquire both resources. 5
6
Reusable Resources • Used by only one process at a time and not depleted by that use • Processes obtain resources that they later release for reuse by other processes • Processors, I/O channels, main and secondary memory, devices, and data structures such as files, databases, and semaphores • Deadlock occurs if each process holds one resource and requests the other 7
Example of Deadlock 8
Another Example of Deadlock • Space is available for allocation of 200 Kbytes, and the following sequence of events occur P 1 P 2 . . . Request 80 Kbytes; Request 70 Kbytes; Request 60 Kbytes; Request 80 Kbytes; . . . • Deadlock occurs if both processes progress to their second request 9
Consumable Resources • Created (produced) and destroyed (consumed) • Interrupts, signals, messages, and information in I/O buffers • Deadlock may occur if a Receive message is blocking • May take a rare combination of events to cause deadlock 10
Example of Deadlock • Deadlock occurs if receive is blocking P 1 P 2 . . . Receive(P 2); Receive(P 1); Send(P 2, M 1); Send(P 1, M 2); . . . 11
Resource Allocation Graphs • Directed graph that depicts a state of the system of resources and processes 12
Resource Allocation Graphs 13
Conditions for Deadlock • Mutual exclusion – Only one process may use a resource at a time • Hold-and-wait – A process may hold allocated resources while awaiting assignment of others • No preemption – No resource can be forcibly removed form a process holding it 14
Conditions for Deadlock • Circular wait – A closed chain of processes exists, such that each process holds at least one resource needed by the next process in the chain 15
16
Possibility of Deadlock • Mutual Exclusion • No preemption • Hold and wait 17
Existence of Deadlock • • Mutual Exclusion No preemption Hold and wait Circular wait 18
Deadlock Prevention • Mutual Exclusion – Must be supported by the operating system • Hold and Wait – Require a process request all of its required resources at one time 19
Deadlock Prevention • No Preemption – Process must release resource and request again – Operating system may preempt a process to require it releases its resources • Circular Wait – Define a linear ordering of resource types 20
Deadlock Avoidance • A decision is made dynamically whether the current resource allocation request will, if granted, potentially lead to a deadlock • Requires knowledge of future process request 21
Two Approaches to Deadlock Avoidance • Do not start a process if its demands might lead to deadlock • Do not grant an incremental resource request to a process if this allocation might lead to deadlock 22
Resource Allocation Denial • Referred to as the banker’s algorithm • State of the system is the current allocation of resources to process • Safe state is where there is at least one sequence that does not result in deadlock • Unsafe state is a state that is not safe 23
Determination of a Safe State Initial State 24
Determination of a Safe State P 2 Runs to Completion 25
Determination of a Safe State P 1 Runs to Completion 26
Determination of a Safe State P 3 Runs to Completion 27
Determination of an Unsafe State 28
Determination of an Unsafe State 29
Deadlock Avoidance Logic 30
Deadlock Avoidance Logic 31
Deadlock Avoidance • Maximum resource requirement must be stated in advance • Processes under consideration must be independent; no synchronization requirements • There must be a fixed number of resources to allocate • No process may exit while holding resources 32
Deadlock Detection 33
Strategies once Deadlock Detected • Abort all deadlocked processes • Back up each deadlocked process to some previously defined checkpoint, and restart all process – Original deadlock may occur • Successively abort deadlocked processes until deadlock no longer exists • Successively preempt resources until deadlock no longer exists 34
Selection Criteria Deadlocked Processes • Least amount of processor time consumed so far • Least number of lines of output produced so far • Most estimated time remaining • Least total resources allocated so far • Lowest priority 35
Strengths and Weaknesses of the Strategies 36
Dining Philosophers Problem 37
Dining Philosophers Problem 38
Dining Philosophers Problem 39
Dining Philosophers Problem 40
Dining Philosophers Problem 41
UNIX Concurrency Mechanisms • • • Pipes Messages Shared memory Semaphores Signals 42
43
Linux Kernel Concurrency Mechanisms • Includes all the mechanisms found in UNIX • Atomic operations execute without interruption and without interference 44
Linux Atomic Operations 45
Linux Atomic Operations 46
Linux Kernel Concurrency Mechanisms • Spinlocks – Used for protecting a critical section 47
48
Linux Kernel Concurrency Mechanisms 49
Solaris Thread Synchronization Primitives • Mutual exclusion (mutex) locks • Semaphores • Multiple readers, single writer (readers/writer) locks • Condition variables 50
51
52
- Deadlock and starvation
- Deadlock and starvation
- Deadlock summary by chapters
- Starvation vs deadlock
- Deadlock prevention and avoidance
- Deadlock vs livelock
- Starvation deadlock
- Starvation method of extinguishing fire
- Ventilator waveform analysis
- A natural physical drive that prevents starvation
- Starvation bmi
- Starvation diabetes mellitus
- Excoriate mnemonic
- Concurrency control and recovery in database systems
- Concurrency control adalah
- Ccs milner
- Safety and liveness in concurrency
- Transactions and concurrency control in distributed systems
- Transaction management and concurrency control in dbms
- Transaction concurrency
- Special segments and points of concurrency
- Transaction management and concurrency control
- Deadlock chapter 37
- The place where all three altitudes meet is called the
- Define point of concurrency
- Concurrency in web applications
- Concurrency definition geometry
- Ue4 mutex
- Unix concurrency mechanisms
- Pitfalls of lock based protocol
- Concurrency control in distributed databases
- Concurrency control in distributed transactions
- Ada concurrency
- Advanced state
- Concurrency
- Subprogram level concurrency
- 5-3 concurrent lines medians and altitudes
- Concurrency of angle bisectors theorem
- Semaphore concurrency
- Concurrency visualizer
- Concurrency can occur at
- Time stamping in database
- Non concurrency endorsement
- Concurrency issues in java
- Youjip won
- Concurrency
- Concurrency monitor
- Concurrency vs parallelism in os
- Statement level concurrency
- Statement level concurrency
- Statement level concurrency
- Cohen "torrent"
- Microsoft flow concurrency control