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


SVG not supported

Login to reply

👍?
helpful
11:05pm Fri 8th Sep, Minn MKM.

I would assume this is what the sample solution would look like if it only took 20usecs to write the data spawn 'cal', pid0.NEW->READY, transition takes 0usecs Total Time: 0 pid0.READY->RUNNING, transition takes 5usecs Total Time: 1, no process running Total Time: 2, no process running Total Time: 3, no process running Total Time: 4, no process running Total Time: 5, no process running Total Time: 5 pid0 now on CPU, gets new timequantum Total Time: 6, CPU Counting, CPU Count=1 Total Time: 7, CPU Counting, CPU Count=2 Total Time: 8, CPU Counting, CPU Count=3 Total Time: 9, CPU Counting, CPU Count=4 Total Time: 10, CPU Counting, CPU Count=5 Total Time: 11, CPU Counting, CPU Count=6 Total Time: 12, CPU Counting, CPU Count=7 Total Time: 13, CPU Counting, CPU Count=8 Total Time: 14, CPU Counting, CPU Count=9 Total Time: 15, CPU Counting, CPU Count=10 Total Time: 16 write 2000bytes, pid0.RUNNING->BLOCKED, transition takes 10usecs Total Time: 17 Total Time: 18 Total Time: 19 Total Time: 20 Total Time: 21 Total Time: 22 Total Time: 23 Total Time: 24 Total Time: 25 Total Time: 26 Total Time: 26 device.terminal acquiring DATABUS, writing 2000 bytes, will take 20 usecs Total Time: 27 Total Time: 28 Total Time: 29 Total Time: 30 Total Time: 31 Total Time: 32 Total Time: 33 Total Time: 34 Total Time: 35 Total Time: 36 Total Time: 37 Total Time: 38 Total Time: 39 Total Time: 40 Total Time: 41 Total Time: 42 Total Time: 43 Total Time: 44 Total Time: 45 Total Time: 46 Total Time: 46 device.terminal completed writing, DATABUS now idle Total Time: 46 pid0.BLOCKED->READY, transition takes 10usecs Total Time: 47 Total Time: 48 Total Time: 49 Total Time: 50 Total Time: 51 Total Time: 52 Total Time: 53 Total Time: 54 Total Time: 55 Total Time: 56 Total Time: 56 pid0.READY->RUNNING, transition takes 5usecs Total Time: 56 pid0 now on CPU, gets new timequantum Total Time: 57, CPU Counting, CPU Count=11 Total Time: 58, CPU Counting, CPU Count=12 Total Time: 59, CPU Counting, CPU Count=13 Total Time: 60, CPU Counting, CPU Count=14 Total Time: 61, CPU Counting, CPU Count=15 Total Time: 62, CPU Counting, CPU Count=16 Total Time: 63, CPU Counting, CPU Count=17 Total Time: 64, CPU Counting, CPU Count=18 Total Time: 65, CPU Counting, CPU Count=19 Total Time: 66, CPU Counting, CPU Count=20 Total Time: 67 exit, pid0.RUNNING->EXIT, transition takes 0usecs Measurements: 67 29 Also in the sample solution I noticed this @00*0*0*6 + OS @00*0*0*6 device.terminal acquiring DATABUS, writeing 2000 bytes, will take 687usecs (20+667) @00*0*0*6 idle @00*0*0*7 idle it doesn't start counting until the second idle. Should I take this into consideration?

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  8:08AM Aug 25 2024
Privacy policy