It's UWAweek 42 (2nd semester, week 12)

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 the 2 articles in this topic
Showing 2 of 676 articles.
Currently 13 other people reading this forum.


 UWA week 41 (2nd semester, week 11) ↓
SVG not supported

Login to reply

👍?
helpful
6:11pm Mon 7th Oct, Chenjun H.

Hi, Just 2 questions about the assignment, With the global least recently used eviction policy, does this only occur when we try to add a page already in the memory to the memory? Also, since the output is only interested in the ram, what is the purpose of the disk? Can't we simulate the virtual memory just using a ram array, since no information is stored in the pages? Thanks


SVG not supported

Login to reply

👍?
helpful
7:13pm Mon 7th Oct, Joshua N.

"Chenjun Hou" <23*6*8*9@s*u*e*t*u*a*e*u*a*> wrote:
> Hi, Just 2 questions about the assignment, > > With the global least recently used eviction policy, does this only occur when we try to add a page already in the memory to the memory?
Occurs when RAM is full and you are trying to load a new page into memory. E.g. If page 0 of process zero is in memory and RAM is full and you are trying to load the next page of process 0, then you evict the least recently loaded page of process 0 (in this case page 0) to make room for page 1.
> Also, since the output is only interested in the ram, what is the purpose of the disk? Can't we simulate the virtual memory just using a ram array, since no information is stored in the pages?
Yes, you could, but I'm not sure if that's what Amitava intends. I think he wants you to pass pointers around, which is the only purpose of virtual memory, to store the pointers.
> Thanks
np

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