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 1 other person reading this forum.

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

Login to reply

10:20am Thu 7th Sep, Christopher M.

"Lewei Xu" <23*0*0*8@s*u*e*t*u*a*e*u*a*> wrote:
> Got this answer from a lab fac: The acquisition of the data bus does not require the OS to be on the CPU. It happens in parallel to everything else. I believe it is because it is the device that acquires the data bus, not the CPU.
Yes, thank you lab fac. We don't get enough chance to discuss this in our lectures, and rushed over it because there's so many different types of devices and how they interact with the data-bus (and, in fact, modern systems will have several data-buses operating with different protocols, and at different speeds). In our project, the system-calls of read and write are copying data between a device and RAM. But we've kept the project simpler by not expressly considering RAM transfers (or even cache). As part of (our project's) state transition, the OS can instruct the relevant device to record the number of bytes to transfer (and to/from where), and the device will be informed by the data-bus, itself, when the bus becomes available. Then the devices, amongst themselves, who gets to own the bus. So the data-bus acquisition time (or data transfer time) does not involve the CPU for either the process or the OS.

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