It's UWAweek 19

help2002

This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.
Displaying selected article
Showing 1 of 1168 articles.
Currently 22 other people reading this forum.


SVG not supported

Login to reply

👍x1
helpful
2:25pm Fri 8th Sep, Marc L.
✅ content verified by our teaching staff  

Never mind, There is no mistake in the sample solution. In the clarifications:
>unblock any sleeping processes >unblock any processes waiting for all their spawned processes (children) to terminate >unblock any completed I/O >commence any pending I/O >commence/resume the next READY process >otherwise the CPU remains idle...
This means that each time the CPU is idle, we only unblock the processes that can be unblocked AT THAT TIME. If anything becomes unblocked, we commence the running of the next process in the ready queue. We do not check again if anything can be unblocked despite the system time increasing. We only check if anything can be unblocked the next time the CPU is idle.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy