OS Organization Chapter 6 Part II: Deadlock Prevention

Deadlock: Design conditions that create the swamps for deadlock to occur:

Deadlock: The Scheduling condition that go to the swamps

Deadlock: What conditions are need for the possibility of deadlock?

Deadlock: What conditions are need for the existence  of deadlock?

Deadlock to be possible: Only one process may use a resource at a time. No process may access a resource unit that has been allocated to another process. Name the condition of policy(?)

Deadlock to be possible: A process may hold allocated resources while awaiting assignment of other resources. Name the condition of policy(?)

Deadlock to be possible: No resource can be forcibly removed from a process holding it. Name the condition of policy(?)

The three conditions of policy: mutual exclusion, hold and wait, and no preemption are said to be ___?___ but not ___?___  for a deadlock to occur.

Deadlock Prevention: The strategy of deadlock prevention is, simply put, to:

Deadlock to exist: For deadlock to exist this condition of policy is needed(?).

Deadlock to exist: Define Circular Wait:

Deadlock Prevention: In deadlock prevention mutual exclusion cannot be disallowed. If access to a resource requires mutual exclusion, then mutual exclusion must be supported by the OS.(T/F)

Deadlock Prevention: In deadlock prevention, the hold and wait condition can be prevented by requiring that a process request all of its required resources at one time, and blocking the process until all requests can be granted simultaneously. This approach is inefficient in three ways: