It's UWAweek 10 (1st semester, week 2)


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

2:28pm Thu 7th Sep, Christopher M.

> If a process is moving from RUNNING -> DATABUS, does it immediately start its data transfer (if the databus is vacant)? Based on the clarifications it seemed to me that the process will wait in the DATABUS until the CPU becomes idle (after finishing any remaining processes in the ready queue) before commencing I/O. However, the sample solution seems to suggest otherwise? > > Perhaps this is just my misunderstanding! Any clarification would be brilliant!
A few things: - there is no state named 'DATABUS' - the data-bus is a 'wire', so a process cannot be 'in' it. - your process would move from RUNNING->BLOCKED. - a process waiting to acquire the data-bus does not have wait for the READY queue to be empty. - the Clarification of 4th Sept states when a blocked process *may* acquire the data-bus.

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