Global Environment Model. MUTUAL EXCLUSION PROBLEM The operations used by processes to access to common resources (critical sections) must be mutually.

Slides:



Advertisements
Similar presentations
1 Interprocess Communication 1. Ways of passing information 2. Guarded critical activities (e.g. updating shared data) 3. Proper sequencing in case of.
Advertisements

Chapter 5 Concurrency: Mutual Exclusion and Synchronization Operating Systems: Internals and Design Principles, 6/E William Stallings Patricia Roy Manatee.
Operating Systems Part III: Process Management (Process Synchronization)
Concurrency: Mutual Exclusion and Synchronization Chapter 5.
1 Implementations: User-level Kernel-level User-level threads package each u.process defines its own thread policies! flexible mgt, scheduling etc…kernel.
Ch. 7 Process Synchronization (1/2) I Background F Producer - Consumer process :  Compiler, Assembler, Loader, · · · · · · F Bounded buffer.
Chapter 2 Processes and Threads
Chapter 6: Process Synchronization
Background Concurrent access to shared data can lead to inconsistencies Maintaining data consistency among cooperating processes is critical What is wrong.
5.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts with Java – 8 th Edition Chapter 5: CPU Scheduling.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 6: Process Synchronization.
EEE 435 Principles of Operating Systems Interprocess Communication Pt II (Modern Operating Systems 2.3)
Process Synchronization. Module 6: Process Synchronization Background The Critical-Section Problem Peterson’s Solution Synchronization Hardware Semaphores.
Interprocess Communication
1 Concurrency: Mutual Exclusion and Synchronization Chapter 5.
Informationsteknologi Wednesday, September 26, 2007 Computer Systems/Operating Systems - Class 91 Today’s class Mutual exclusion and synchronization 
EEE 435 Principles of Operating Systems Interprocess Communication Pt I (Modern Operating Systems 2.3)
Concurrency, Race Conditions, Mutual Exclusion, Semaphores, Monitors, Deadlocks Chapters 2 and 6 Tanenbaum’s Modern OS.
1 Concurrency: Mutual Exclusion and Synchronization Chapter 5.
Synchronization Principles. Race Conditions Race Conditions: An Example spooler directory out in 4 7 somefile.txt list.c scores.txt Process.
1 CS 333 Introduction to Operating Systems Class 4 – Synchronization Primitives Semaphores Jonathan Walpole Computer Science Portland State University.
Chapter 2.3 : Interprocess Communication
1 Chapter 6: Concurrency: Mutual Exclusion and Synchronization Operating System Spring 2007 Chapter 6 of textbook.
Jonathan Walpole Computer Science Portland State University
Jonathan Walpole Computer Science Portland State University
Race Conditions CS550 Operating Systems. Review So far, we have discussed Processes and Threads and talked about multithreading and MPI processes by example.
1 Outline Processes Threads Inter-process communication (IPC) Classical IPC problems Scheduling.
1 Interprocess Communication Race Conditions Two processes want to access shared memory at same time.
Instructor: Umar KalimNUST Institute of Information Technology Operating Systems Process Synchronization.
1 Race Conditions/Mutual Exclusion Segment of code of a process where a shared resource is accessed (changing global variables, writing files etc) is called.
Operating Systems CSE 411 CPU Management Oct Lecture 13 Instructor: Bhuvan Urgaonkar.
© Janice Regan, CMPT 300, May CMPT 300 Introduction to Operating Systems Introduction to Concurrency.
Process Synchronization Continued 7.2 Critical-Section Problem 7.3 Synchronization Hardware 7.4 Semaphores.
1 Concurrency: Mutual Exclusion and Synchronization Module 2.2.
Operating Systems ECE344 Ashvin Goel ECE University of Toronto Mutual Exclusion.
Concurrency: Mutual Exclusion and Synchronization Chapter 5.
Silberschatz, Galvin and Gagne  Operating System Concepts Chapter 7: Process Synchronization Background The Critical-Section Problem Synchronization.
Chapter 7 -1 CHAPTER 7 PROCESS SYNCHRONIZATION CGS Operating System Concepts UCF, Spring 2004.
Chapter 6 – Process Synchronisation (Pgs 225 – 267)
CSNB334 Advanced Operating Systems 4. Concurrency : Mutual Exclusion and Synchronization.
2.3 interprocess communcation (IPC) (especially via shared memory & controlling access to it)
Background Concurrent access to shared data may result in data inconsistency Maintaining data consistency requires mechanisms to ensure the orderly execution.
CS399 New Beginnings Jonathan Walpole. 2 Concurrent Programming & Synchronization Primitives.
U NIVERSITY OF M ASSACHUSETTS A MHERST Department of Computer Science Computer Systems Principles Synchronization Emery Berger and Mark Corner University.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 6: Process Synchronization.
1 Processes and Threads Part II Chapter Processes 2.2 Threads 2.3 Interprocess communication 2.4 Classical IPC problems 2.5 Scheduling.
Operating System Concepts and Techniques Lecture 13 Interprocess communication-2 M. Naghibzadeh Reference M. Naghibzadeh, Operating System Concepts and.
Process Synchronization. Objectives To introduce the critical-section problem, whose solutions can be used to ensure the consistency of shared data To.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition Chapter 6: Process Synchronization.
Implementing Mutual Exclusion Andy Wang Operating Systems COP 4610 / CGS 5765.
Mutual Exclusion -- Addendum. Mutual Exclusion in Critical Sections.
Chapter 6 Synchronization Dr. Yingwu Zhu. The Problem with Concurrent Execution Concurrent processes (& threads) often access shared data and resources.
CS703 – Advanced Operating Systems
Chapter 5: Process Synchronization
Lecture 12: Peterson’s Solution and Hardware Support
Lecture 13: Producer-Consumer and Semaphores
Lecture 11: Mutual Exclusion
Concurrency: Mutual Exclusion and Synchronization
Jonathan Walpole Computer Science Portland State University
Lecture 22 Syed Mansoor Sarwar
Module 7a: Classic Synchronization
Process Synchronization
Jonathan Walpole Computer Science Portland State University
Global Environment Model
Concurrency: Mutual Exclusion and Process Synchronization
Chapter 6: Process Synchronization
Lecture 12: Peterson’s Solution and Hardware Support
Lecture 13: Producer-Consumer and Semaphores
CS333 Intro to Operating Systems
Chapter 6: Synchronization Tools
Presentation transcript:

Global Environment Model

MUTUAL EXCLUSION PROBLEM The operations used by processes to access to common resources (critical sections) must be mutually exclusive in time

A A B B t t  No assumptions should be made about relative process speed  A, B critical sections

Example  During their execution P1 and P2 access a common variable count(i.v.=O) and increment it by 1

Example  When P1 and P2 terminate their executions count must be incremented by 2 count=2

Note that the increment of count, when P1 execute it, may be implemented in machine language as: reg1 = count reg1 = reg1 +1 count = reg1 Where reg1 is a local CPU register used by P1

Similarly the increment of count, when P2 executes it, may be implemented in machine language as: reg2 = count reg2 = reg2 +1 count = reg2 where reg2 is a local CPU register used by P2

The concurrent execution of the statement ++count is equivalent to a sequential execution where the statements can be interleaved in any arbitrary order

TO:reg1=count(reg1=O) (P1) T1:reg2=count(reg2=O) (P2) T2:reg2=reg2+1(reg2=1) (P2) T3:count=reg2(count=1) (P2) T4:reg1=reg1+1(reg1=1) (P1) T5: count=reg1(count=1) (P1)

RACE CONDITION: Several processes concurrently access and manipulate the same data

RACE CONDITION: The outcome of the execution depends on the particular order in wich the access takes place

To prevent race conditions, we need to assure that only one process at a time can be operating on the same variable count

To grant that invariant, we need some form of process synchronization

SOLUTION TO THE MUTUAL EXCLUSION PROBLEM P 1 while (busy ==1); busy =1 ; busy =O; busy = 1 the resource is busy busy = O the resource is free

P 2 while (busy ==1); busy =1 ; busy =O;

T O : P 1 executes while and busy=O T 1 : P 2 executes while and busy=O T 2 : P 1 set busy=1 and accesses to A T 3 : P 2 set busy=1 and accesses to B Both processes have simultaneous access to their critical section

TSL (Test and Set Lock) Instruction that reads and modifies the contents of a memory word in an indivisible way

The CPU, while executing the TSL instruction, locks the memory bus to prohibit other CPUs from accessing memory until the instruction is completed

TSL R, x: It reads the content of x into the register R and then stores a non zero value at that memory address

The operations of reading a word and storing into it are garantee to be indivisible by the hardware level TSL R, x:

lock(x): lock(x), unlock(x): (copy x to register and set x=1) TSL register, x CMP register,O (if non zero the cycle is restarted) (return to caller; critical region entered) (was x zero?) JNE lock RET

unlock(x): (store a O in x)MOVE x, O (return to caller)RET

P 1 lock(x); ; unlock (x); Soluzione con lock(x) e unlock(x):

P 2 lock(x); ; unlock (x); Soluzione con lock(x) e unlock(x):

SOLUTION PROPERTIES  busy waiting  multiprocessor systems  “very shorts” critical sections

x x R R P1P1 P2P2 PR 1 PR n

integer non negative variable, initialized to a nonnegative value s.value SEMAPHORES A semaphor s is a

s is associated with a waiting list, in wich are linked the PCBs of processes blocked on s. s.queue s

A semaphore s is accessed only via two standard operations  P (s)  V (s)

P(s) If s.value>O the process continues its execution, if s.value=O the process is blocked in the s.queue

V(s) A process in the s.queue is waked and extracted; its state is modified from blocked to ready

void P(s) { if (s.value==O) ; else s.value= s.value-1; }

void V(s) { if ( ) ; else s.value = s.value + 1; }

As a consequence of the execution of a V(s) the state of the process does not change

The decision of wich process is to be extracted from the s.queue is taken with a FIFO policy

P (mutex) V (mutex) MUTUAL EXCLUSION mutex: semaphore associated to the shared resource (i. v. mutex=1)

P1P2 P(mutex)P(mutex) V (mutex) P3 P (mutex) V (mutex)

P and V must be indivisible operations The modification of the value of the semaphore and the possible blocking or waking up of a process must be indivisible operations

(mutex.value, mutex.queue) P,V: critical sections with reference to the data structure represented by mutex

Disabling interrupts (when P,V are executing on the same processor) INDIVISIBILITY OF P AND V BY

Using lock(x), unlock(x)( when P,V are executing on different processors) INDIVISIBILITY OF P AND V BY

lock(x); P (mutex); unlock(x); ; lock(x); V (mutex); unlock(x); indivisible P,V

x x R R P1P1 P2P2 PR 1 PR n mutex