Monitors High-level synchronization construct that allows the safe sharing of an

abstract data type among concurrent processes.

monitor monitor-name{

shared variable declarationsprocedure body P1 (…) {

. . .}procedure body P2 (…) {

. . .} procedure body Pn (…) {

. . .} {

initialization code}

}

Monitors To allow a process to wait within the monitor, a

condition variable must be declared, ascondition x, y;

Condition variable can only be used with the operations wait and signal.• The operation

x.wait();means that the process invoking this operation is suspended until another process invokes

x.signal();• The x.signal operation resumes exactly one suspended

process. If no process is suspended, then the signal operation has no effect.

Schematic View of a Monitor

Dining Philosophers Examplemonitor dp

{enum {thinking, hungry, eating} state[5];condition self[5];void pickup(int i) // following slidesvoid putdown(int i) // following slidesvoid test(int i) // following slidesvoid init() {

for (int i = 0; i < 5; i++)state[i] = thinking;

}}

Dining Philosophersvoid pickup(int i) {

state[i] = hungry;test[i];if (state[i] != eating)

self[i].wait();}

void putdown(int i) {state[i] = thinking;// test left and right neighborstest((i+4) % 5);test((i+1) % 5);

}

void test(int i) { if ( (state[(I + 4) % 5] != eating)

&& (state[i] == hungry)&& (state[(i + 1) % 5] != eating)) {

state[i] = eating;self[i].signal();

}}

The POSIX API for Synchronization –Semaphores#include <semaphores.h>

int sem_init(sem_t *sem,int pshared,unsigned int value);

int sem_wait(sem_t *sem);

int sem_post(sem_t *sem);

int sem_destroy(sem_t *sem);

Mutexes#include <semaphores.h>

int pthread_mutex_init(pthread_mutex_t *mutex, const pthread_mutexattr_t

*mutexattr);

int pthread_mutex_lock(pthread_mutex_t * mutex);

int pthread_mutex_unlock(pthread_mutex_t * mutex);

int pthread_mutex_destroy(pthread_mutex_t * mutex);

Condition variablesint pthread_cond_init (pthread_cond_t *cptr,

pthread_condattr_t *attr);

int pthread_cond_wait (pthread_cond_t *cptr, pthread_mutex_t *mptr);

int pthread_cond_signal (pthread_cond_t *cptr);

int pthread_cond_broadcast (pthread_cond_t *cptr);

int pthread_cond_destroy (pthread_cond_t *cptr);

Methods of Handling Deadlocks Deadlock Characterization

• 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 {P0, P1, …, P0} of waiting processes such that P0 is waiting for a resource that is held by P1, P1 is waiting for a resource that is held by P2, …, Pn–1 is waiting for a resource that is held by Pn, and P0 is waiting for a resource that is held by P0.

Resource-Allocation Graph Process

Resource Type with 4 instances

Pi requests instance of Rj

Pi is holding an instance of RjPi

Pi

Rj

Rj

Example of a Resource Allocation Graph No Deadlock DeadLock

Resource Allocation Graph With A Cycle But No Deadlock 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.

So what can we do ? 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.

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

Deadlock Prevention 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.

prevention strategies are not practical

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

• The deadlock-avoidance algorithm dynamically examines the resource-allocation state to ensure that there can never be a circular-wait condition.

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

• Avoidance ensure that a system will never enter an unsafe state.

Banker’s Algorithm – Assumptions 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

Banker’s AlgorithmExample - P2 requests 1 R3

R1 R2 R3 R1 R2 R3 R1 R2 R3

P1 3 2 2 P1 1 0 0 9 3 6

P2 6 1 3 P2 6 1 1 Resources

P3 3 1 4 P3 2 1 1

P4 4 2 2 P4 0 0 2 R1 R2 R3

Claim matrix

Allocation matrix

0 1 2

Available vector

Assume request is granted.Is it ‘safe’ or not?

R1 R2 R3 R1 R2 R3 R1 R2 R3

P1 3 2 2 P1 1 0 0 9 3 6

P2 6 1 3 P2 6 1 2 Resources

P3 3 1 4 P3 2 1 1

P4 4 2 2 P4 0 0 2 R1 R2 R3

Claim matrix

Allocation matrix

0 1 1

Available vector

P1 cannot go first. Resources not enough

R1 R2 R3 R1 R2 R3 R1 R2 R3

P1 3 2 2 P1 1 0 0 9 3 6

P2 6 1 3 P2 6 1 2 Resources

P3 3 1 4 P3 2 1 1

P4 4 2 2 P4 0 0 2 R1 R2 R3

Claim matrix

Allocation matrix

0 1 1

Available vector

State after P2 runs to completionR1 R2 R3 R1 R2 R3 R1 R2 R3

P1 3 2 2 P1 1 0 0 9 3 6

P2 0 0 0 P2 0 0 0 Resources

P3 3 1 4 P3 2 1 1

P4 4 2 2 P4 0 0 2 R1 R2 R3

Claim matrix

Allocation matrix

6 2 3

Available vector

State after P1 runs to completionR1 R2 R3 R1 R2 R3 R1 R2 R3

P1 0 0 0 P1 0 0 0 9 3 6

P2 0 0 0 P2 0 0 0 Resources

P3 3 1 4 P3 2 1 1

P4 4 2 2 P4 0 0 2 R1 R2 R3

Claim matrix

Allocation matrix

7 2 3

Available vector

State after P3 runs to completionR1 R2 R3 R1 R2 R3 R1 R2 R3

P1 0 0 0 P1 0 0 0 9 3 6

P2 0 0 0 P2 0 0 0 Resources

P3 0 0 0 P3 0 0 0

P4 4 2 2 P4 0 0 2 R1 R2 R3

Claim matrix

Allocation matrix

9 3 4

Available vector

State after P4 runs to completionR1 R2 R3 R1 R2 R3 R1 R2 R3

P1 0 0 0 P1 0 0 0 9 3 6

P2 0 0 0 P2 0 0 0 Resources

P3 0 0 0 P3 0 0 0

P4 0 0 0 P4 0 0 0 R1 R2 R3

Claim matrix

Allocation matrix

9 3 6

Available vector

A safe state! Grant P2 an R3

Deadlock Detection OS does not prevent deadlocks. OS grants resources whenever possible. OS checks for deadlock by checking for

circular waiting by either method:1.Checking at resource request

• early detection of deadlock

• frequent checks consume processor time

2.Checking periodically

Deadlock detection – example - current situation

R1 R2 R3 R4 R5 R1 R2 R3 R4 R5 R1 R2 R3 R4 R5

P1 0 1 0 0 1 P1 1 0 1 1 0 2 1 1 2 1

P2 0 0 1 0 1 P2 1 1 0 0 0 Resource vector

P3 0 0 0 0 1 P3 0 0 0 1 0

P4 1 0 1 0 1 P4 0 0 0 0 0 R1 R2 R3 R4 R5

Requests

(these are actual requests not

theoretical claims as in Bankers algorithm)

Allocation 0 0 0 0 1

Available vector

Deadlock detection –Step1: Mark P4

R1 R2 R3 R4 R5 R1 R2 R3 R4 R5 R1 R2 R3 R4 R5

P1 0 1 0 0 1 P1 1 0 1 1 0 2 1 1 2 1

P2 0 0 1 0 1 P2 1 1 0 0 0 Resource vector

P3 0 0 0 0 1 P3 0 0 0 1 0

P4 1 0 1 0 1 P4 0 0 0 0 0 R1 R2 R3 R4 R5

Requests Allocation 0 0 0 0 1

Available vector

Deadlock detection –Step2: P3 is able to continue

R1 R2 R3 R4 R5 R1 R2 R3 R4 R5 R1 R2 R3 R4 R5

P1 0 1 0 0 1 P1 1 0 1 1 0 2 1 1 2 1

P2 0 0 1 0 1 P2 1 1 0 0 0 Resource vector

P3 0 0 0 0 1 P3 0 0 0 0 0

P4 1 0 1 0 1 P4 0 0 0 0 0 R1 R2 R3 R4 R5

Requests Allocation 0 0 0 1 1

Available vector

Deadlock detection – Step3: P1&P2 cannot continue

R1 R2 R3 R4 R5 R1 R2 R3 R4 R5 R1 R2 R3 R4 R5

P1 0 1 0 0 1 P1 1 0 1 1 0 2 1 1 2 1

P2 0 0 1 0 1 P2 1 1 0 0 0 Resource vector

P3 0 0 0 0 1 P3 0 0 0 0 0

P4 1 0 1 0 1 P4 0 0 0 0 0 R1 R2 R3 R4 R5

Requests Allocation 0 0 0 1 1

Available vectorP1&P2 must have a deadlock!

OS options after a deadlock is detected Abort all deadlocked processes Back up all deadlocked processes to some

previously defined checkpoint Successively abort deadlocked processes until

deadlock no longer exists Successively preempt resources until deadlock

no longer exists

OS options: which deadlocked process to abort? 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