It's UWAweek 9 (1st semester, week 1)


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 3 other people reading this forum.

 UWA week 36 (2nd semester, mid-semester break) ↓
SVG not supported

Login to reply

8:18am Sat 9th Sep, Jacob R.

The CPU moves to IDLE every time a process finishes its timequantum or executes a syscall (after moving the process). It then executes in the order of these steps: 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... And it always executes in this order. So if after running a process, it can then wake something up, it will. The last thing that occurs in IDLE is moving the next process from READY into RUNNING. So it kinda has the least priority. Hence you don't just get processes consistently on the CPU not letting anything wake up.

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  5:07AM Sep 06 2023
Privacy policy