More Synchronisation Massey University更多的同步梅西大学.pptVIP

159.335 More Synchronisation Last time: bounded buffer, readers-writers, dining philosophers Today: sleeping barber, monitors What is the sleeping barber problem? 1 barber N waiting chairs No customers - barber sleeps Customer arrives - wakes barber if asleep Otherwise if empty chair sit down, otherwise leave shop. Barber Thread Global Variables Semaphore customers = 0; // no of waiting customers Semaphore barbers = 0; // no of waiting barbers (0 or 1) Semaphore mutex = 1; // protect critical sections int waiting=0; Barber void barber() { while(1) { wait(customers); // wait for a customer wait(mutex); // protect waiting waiting--; signal(barbers); // tell customer signal(mutex); // release lock on waiting cut_hair(); } } Customer Thread Customer void customer() { wait(mutex); // in CS if(waiting NO_CHAIRS) { // if no free chairs leave waiting++; // one more waiting customer signal(customers); // wakeup barber if necessary signal(mutex); // release lock wait(barbers); // wait until barber is free get_haircut(); } else { signal(mutex); } } Can Synchronisation be made easier? What is a Monitor? A High level synchronisation construct. i.e. Part of a programming language. Why? Semaphores are confusing because 1. Two uses - mutex and ipc 2. Can forget one of them or get in wrong order. How? Mutex: Put critical sections into separate functions and group together. This is called a monitor. IPC: use special variables for wait and signal. These are called condition variables. Monitor for Produce-Consumer monitor ProducerConsumer { condition full, empty; int count=0; void enter() { if (count == N) wait(full); ...enter item... count++; if (count == 1) signal(empty); } void remove() { if (count == 0) wait(empty); ...remove item... count--; if (count == N-1) signal(full); } } Monitor for Produce-Consumer void producer() { while(1) { ...produce item..