Virtual Memory: Page Replacement. CSSE 332 Operating Systems Rose-Hulman Institute of Technology

Transcription

1 Virtual Memory: Page Replacement CSSE 332 Operating Systems Rose-Hulman Institute of Technology

2 Announcements Project E & presentation are due Wednesday Team reflections due Monday, May 19

3 The need for page replacement Page replacement find some page in memory, but not really in use, swap it out algorithm performance want an algorithm that will result in minimum number of page faults Use modify (dirty) bit to reduce overhead of page transfers only modified pages are written to disk

4 Basic page replacement 1. Find the location of the desired page on disk 2. Find a free frame: - If there is a free frame, use it - If there is no free frame, use a page replacement algorithm to select a victim frame 3. Bring the desired page into the (newly) free frame; update the page and frame tables 4. Resume the process

5 Page replacement

6 Page replacement algorithms Want lowest page-fault rate Evaluate algorithm by running it on a particular string of page references (reference string) and computing the number of page faults on that string In all our examples, the reference string is 1, 2, 3, 4, 1, 2, 5, 1, 2, 3, 4, 5!

7 Page faults vs number of frames

8 First-in-first-out (FIFO) algorithm Reference string: 1, 2, 3, 4, 1, 2, 5, 1, 2, 3, 4, 5 3 frames (3 pages can be in memory at a time per process) page faults 4 frames Belady s Anomaly: more frames more page faults page faults

9 FIFO page replacement

10 FIFO shows Belady s anomaly

11 Optimal algorithm Replace page that will not be used for longest period of time 4 frames example 1, 2, 3, 4, 1, 2, 5, 1, 2, 3, 4, page faults How do you know this? Used for measuring how well your algorithm performs

12 Optimal page replacement

13 Least recently used (LRU) algorithm Reference string: 1, 2, 3, 4, 1, 2, 5, 1, 2, 3, 4, ! ! 5 4! ! 3 3 Counter implementation Every page entry has a counter; every time page is referenced through this entry, copy the clock into the counter When a page needs to be changed, look at the counters to determine which are to change

14 LRU page replacement

15 LRU approxima,on algorithm Clock policy: Every frame has a reference bit (R) that is set to 1 when a page is first loaded in it R is set to 1 every time the page is referenced Put pages on a circular buffer in the form of a clock with a hand (pointer) referencing the next page Next page: the page after the one that was just replaced in the circular buffer When page fault occurs, if next page has R = 0 then replace otherwise set R = o and advance the next page pointer. Keep advancing until locate page with R = 0.

16 Second-chance (clock) pagereplacement algorithm

17 Resident set management Resident set size How many pages per process in main memory Replacement scope When bringing in a new page, should the page being replaced be that of the process that caused the page fault or could it belong to any process

18 Fixed allocation of frames Equal allocation For example, if there are 100 frames and 5 processes, give each process 20 frame Proportional allocation Allocate according to the size of process

19 Priority allocation Use a proportional allocation scheme using priorities rather than size If process P i generates a page fault, select for replacement one of its frames select for replacement a frame from a process with lower priority number

20 Global vs. local allocation Global replacement process selects a replacement frame from the set of all frames; one process can take a frame from another Local replacement each process selects from only its own set of allocated frames

21 Thrashing If a process does not have enough pages, the page-fault rate is very high. This leads to: low CPU utilization operating system thinks that it needs to increase the degree of multiprogramming another process added to the system Thrashing a process is busy swapping pages in and out

22 Thrashing (cont.)

23 Exploi,ng the principle of locality Programs tend to demonstrate temporal and spatial locality of reference Program and data references within a process tend to cluster Only a few pieces of a process will be needed over a short period of time Possible to make intelligent guesses about which pieces will be needed in the future This suggests that virtual memory may work efficiently Q4