(10 marks). Semaphores, Monitors, and Rendezvous IPC can all solve the same classes of problems in that you can implement one facility with one of the others. .Use Monitors to implement the IPC primitives Send, Receive and Reply as defined in class to have zero-capacity semantics. Provide detailed C-like pseudocode. Identify the List Operations that you need (if you need any), but do not implement them. Assume that you have a monitor facility in your programming language, so that you do not need MonEnter and MonLeave, and that messages consist of a pointer to shared space and a buffer length. Assume also that the monitor contains the PCB for all the processes. Define those fields in the PCB which you think are necessary (in particular, condition variables). I've got you started. The implementation is short Monitor IPC /*shared data and initialization/ /*Monitor procedures* char *Send char *Receive int Reply ( (10 marks). Semaphores, Monitors, and Rendezvous IPC can all solve the same classes of problems in that you can implement one facility with one of the others. .Use Monitors to implement the IPC primitives Send, Receive and Reply as defined in class to have zero-capacity semantics. Provide detailed C-like pseudocode. Identify the List Operations that you need (if you need any), but do not implement them. Assume that you have a monitor facility in your programming language, so that you do not need MonEnter and MonLeave, and that messages consist of a pointer to shared space and a buffer length. Assume also that the monitor contains the PCB for all the processes. Define those fields in the PCB which you think are necessary (in particular, condition variables). I've got you started. The implementation is short Monitor IPC /*shared data and initialization/ /*Monitor procedures* char *Send char *Receive int Reply (