It's UWAweek 47

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 828 articles.
Currently 117 other people reading this forum.


 UWA week 42 (2nd semester, week 12) ↓
SVG not supported

Login to reply

👍?
helpful
3:10pm Mon 14th Oct, ANONYMOUS

ANONYMOUS wrote:
> Assume that we had called the same process ID 5 times like so: > > 0 0 0 0 0 > > when we get to that fifth call, since it's already in memory, should we increase the time?
As Amitava said in his clarification email "(1) What happens if all the pages of a process are already in memory and the process id appears again in the input. You can handle this one of two ways, either you can ignore it, or 'bring' the 0th page of the process to RAM again (and the 1st page if the process id appears again ... so on). Either way is acceptable." You can either choose to load it into RAM and increase time or just ignore it
> > like should it be: > > 0, 1, 2, 3, 4 > > or > > 0, 1, 2, 3, 3 (since were not moving values from Virtual Machine to RAM) >
Both are valid
> > Also, in that fifth call, we will still update the last accessed time of that page number in the page table correct? > > so for processID 0 in this example by the fifth call, last accessed time will be as follows: > > (3 or 4), 1, 2, 3
It depends on which way you choose, if you ignore it, you don't load it into the RAM, thus, not using much/any time so it doesn't increase. If you choose to read it, it will increase by 1 as you said in the 2nd point

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