1) Some semaphore implementations provide a function getValue() that returns the current value of a semaphore....

  

Transcribed Image Text:

1) Some semaphore implementations provide a function getValue() that returns the current value of a semaphore. This function may, for instance, be invoked prior to calling wait() so that a process will only call wait() if the value of the semaphore is > 0, thereby preventing blocking while waiting for the semaphore. For example: if (getValue(&sem) wait (&sem); wwwww > 0) wwww What is the problem in this approach? (5 points) 2) Briefly describe what a reader-writer lock is for and why it can be more efficient than semaphores in some cases. (5 points) 1) Some semaphore implementations provide a function getValue() that returns the current value of a semaphore. This function may, for instance, be invoked prior to calling wait() so that a process will only call wait() if the value of the semaphore is > 0, thereby preventing blocking while waiting for the semaphore. For example: if (getValue(&sem) wait (&sem); wwwww > 0) wwww What is the problem in this approach? (5 points) 2) Briefly describe what a reader-writer lock is for and why it can be more efficient than semaphores in some cases. (5 points)

Answer rating: 100% (QA)

The text in the image describes a potential problem with a particular approach to using semaphores Heres a breakdown of the passage Semaphore A semaph... View the full answer