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

 UWA week 35 (2nd semester, week 6) ↓
SVG not supported

Login to reply

12:02pm Thu 31st Aug, ANONYMOUS

Hi just wanted to clarify my understanding of transitions (i.e. a process that is changing state e.g. RUNNING -> BLOCKED). I've read all the posts on this forum (and there have been some previous ones on similar topics) but none of them seem to clarify this: When a transition occurs, to my understanding, the OS performs an operation on the CPU. The duration of this CPU operation is specified in the project requirements (e.g. 5usec for READY -> RUNNING, 10usec for other transitions). Do these OS-triggered transitions need to be queued (on the ready queue). Or do we assume that the transition occurs instantly (taking over what was on the CPU). For example, if a process is moving from BLOCKED -> READY, does the "transition" immediately start taking up CPU time (causing the currently running CPU process to be "put on pause" while this occurs)? Or does this "transition" get "enqueued" onto the ready queue - if so, does the delay in this transition being performed (as it waits to get to the CPU) affect the original process? Hope this makes sense. Any clarification would be amazing!

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