Question: a) Remember this readers-writers synchronization problem from BUX and the reference book. do { wait(mutex); read_count++; if (read.count == 1) wait(rw_mutex); signal (mutex); /* reading

a) Remember this readers-writers synchronization problem from BUX and the reference book. do { wait(mutex); read_count++; if (read.count == 1) wait(rw_mutex); signal (mutex); /* reading is performed / do { wait(rw_mutex); wait(mutex); read_count--; /* writing is performed */ if (read_count == 0) signal (rw_mutex); signal (rw_mutex); signal (mutex); } while (true); } while (true); Figure 5.11 The structure of a writer process. Figure 5.12 The structure of a reader process. This solution solves the critical section problem. However, there is a starvation issue here for the writer process. If there is a steady stream of reader processes in the ready queue, the writer process may starve and may not be able to write. We hope you can solve this starvation issue by applying one restriction in the code. The restriction is that if the writer was waiting for a reader, then that reader cannot read again before the writer completes writing. If more than one reader were reading when the writer was waiting, this restriction applies to all those readers. Update the reader and writer code to implement this restriction. HINTS: You do not need any additional mutex for this but need to use both
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
