help2002

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

1st project Unblocking when idle clarification (both)

2:56pm Fri 8th Sep, Marc L.

In the clarifications:

>When the CPU is idle (no process or the OS is using the CPU), perform the following in this order: >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...

Does this mean that we take the time when the CPU is first IDLE as the only point of reference? For example, if a CPU is IDLE at say t=100 and a sleeping process is gets unblocked, the context change will cause the time to be 110. An I/O completes at say t=105. Do we take t=100 as the point of comparison for the I/O unblocking, or t=110? In other words, do we allow the I/O process to unblock before we put the sleeping process onto running?