Page Replacement. 3/9/07 CSE 30341: Operating Systems Principles

Similar documents
Optimal Algorithm. Replace page that will not be used for longest period of time Used for measuring how well your algorithm performs

Module 9: Virtual Memory

Module 9: Virtual Memory

Background. Virtual Memory (2/2) Demand Paging Example. First-In-First-Out (FIFO) Algorithm. Page Replacement Algorithms. Performance of Demand Paging

Background. Demand Paging. valid-invalid bit. Tevfik Koşar. CSC Operating Systems Spring 2007

Virtual Memory. CSCI 315 Operating Systems Design Department of Computer Science

Page Replacement Algorithms

Basic Page Replacement

Virtual Memory. Virtual Memory. Demand Paging. valid-invalid bit. Virtual Memory Larger than Physical Memory

Chapter 10: Virtual Memory. Background

instruction is 6 bytes, might span 2 pages 2 pages to handle from 2 pages to handle to Two major allocation schemes

Chapter 10: Virtual Memory. Background. Demand Paging. Valid-Invalid Bit. Virtual Memory That is Larger Than Physical Memory

Lecture 17. Edited from slides for Operating System Concepts by Silberschatz, Galvin, Gagne

Where are we in the course?

Chapter 9: Virtual Memory

Chapter 9: Virtual-Memory

Chapter 9: Virtual Memory

Chapter 9: Virtual Memory. Chapter 9: Virtual Memory. Objectives. Background. Virtual-address address Space

Chapter 9: Virtual Memory

Chapter 9: Virtual Memory

Principles of Operating Systems

Virtual Memory. CSCI 315 Operating Systems Design Department of Computer Science

Demand Paging. Valid-Invalid Bit. Steps in Handling a Page Fault. Page Fault. Transfer of a Paged Memory to Contiguous Disk Space

CS370 Operating Systems

First-In-First-Out (FIFO) Algorithm

Chapter 3: Virtual Memory ว ตถ ประสงค. Background สามารถอธ บายข อด ในการท ระบบใช ว ธ การจ ดการหน วยความจ าแบบเสม อนได

CS370 Operating Systems

Chapter 9: Virtual Memory

Chapter 8: Virtual Memory. Operating System Concepts

Virtual Memory - II. Roadmap. Tevfik Koşar. CSE 421/521 - Operating Systems Fall Lecture - XVI. University at Buffalo.

Chapter 9: Virtual Memory. Operating System Concepts 9 th Edition

Operating System Concepts

Virtual Memory. Overview: Virtual Memory. Virtual address space of a process. Virtual Memory

Chapter 9: Virtual-Memory Management. Operating System Concepts 8 th Edition,

Virtual Memory - Overview. Programmers View. Virtual Physical. Virtual Physical. Program has its own virtual memory space.

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

CS420: Operating Systems

Chapter 6: Demand Paging

Virtual Memory. Overview: Virtual Memory. Virtual address space of a process. Virtual Memory. Demand Paging

CS307: Operating Systems

Operating Systems. Overview Virtual memory part 2. Page replacement algorithms. Lecture 7 Memory management 3: Virtual memory

Virtual Memory Outline

CSC Operating Systems Spring Lecture - XIV Virtual Memory - II. Tevfik Ko!ar. Louisiana State University. March 27 th, 2008.

Swapping. Operating Systems I. Swapping. Motivation. Paging Implementation. Demand Paging. Active processes use more physical memory than system has

PAGE REPLACEMENT. Operating Systems 2015 Spring by Euiseong Seo

ADRIAN PERRIG & TORSTEN HOEFLER Networks and Operating Systems ( ) Chapter 6: Demand Paging

Virtual Memory COMPSCI 386

Chapter 9: Virtual Memory. Operating System Concepts 9 th Edition

Chapter 9: Virtual Memory. Operating System Concepts 9th Edition

Chapter 10: Virtual Memory

Chapters 9 & 10: Memory Management and Virtual Memory

Operating System Concepts 9 th Edition

Virtual Memory B: Objec5ves

OPERATING SYSTEM. Chapter 9: Virtual Memory

1. Background. 2. Demand Paging

CS370 Operating Systems

Memory Management. Virtual Memory. By : Kaushik Vaghani. Prepared By : Kaushik Vaghani

ECE 7650 Scalable and Secure Internet Services and Architecture ---- A Systems Perspective. Part I: Operating system overview: Memory Management

Memory management, part 2: outline. Operating Systems, 2017, Danny Hendler and Amnon Meisels

CS6401- Operating System UNIT-III STORAGE MANAGEMENT

Memory Allocation. Copyright : University of Illinois CS 241 Staff 1

Memory management, part 2: outline

Virtual Memory III. Jo, Heeseung

UNIT - IV. What is virtual memory?

e-pg Pathshala Subject: Computer Science Paper: Operating Systems Module 29: Allocation of Frames, Thrashing Module No: CS/OS/29 Quadrant 1 e-text

Chapter 8: Virtual Memory. Operating System Concepts Essentials 2 nd Edition

Operating Systems Virtual Memory. Lecture 11 Michael O Boyle

Operating System - Virtual Memory

Lecture 14 Page Replacement Policies

Memory - Paging. Copyright : University of Illinois CS 241 Staff 1

CS 4410 Operating Systems. Page Replacement (2) Summer 2016 Cornell University

VII. Memory Management

Memory Management Outline. Operating Systems. Motivation. Paging Implementation. Accessing Invalid Pages. Performance of Demand Paging

Practice Exercises 449

Addresses in the source program are generally symbolic. A compiler will typically bind these symbolic addresses to re-locatable addresses.

Chapter 4 Memory Management

Operating Systems. No. 9 ศร ณย อ นทโกส ม Sarun Intakosum

Today. Adding Memory Does adding memory always reduce the number of page faults? FIFO: Adding Memory with LRU. Last Class: Demand Paged Virtual Memory

Memory Management. To improve CPU utilization in a multiprogramming environment we need multiple programs in main memory at the same time.

Page Replacement Chap 21, 22. Dongkun Shin, SKKU

Chapter 9: Virtual Memory

!! What is virtual memory and when is it useful? !! What is demand paging? !! When should pages in memory be replaced?

Last Class: Demand Paged Virtual Memory

ECE7995 Caching and Prefetching Techniques in Computer Systems. Lecture 8: Buffer Cache in Main Memory (I)

Virtual Memory cont d.; File System Interface. 03/30/2007 CSCI 315 Operating Systems Design 1

Roadmap. Tevfik Ko!ar. CSC Operating Systems Spring Lecture - XIV Virtual Memory - I. Louisiana State University.

VIRTUAL MEMORY READING: CHAPTER 9

Virtual or Logical. Logical Addr. MMU (Memory Mgt. Unit) Physical. Addr. 1. (50 ns access)

CSE 120. Translation Lookaside Buffer (TLB) Implemented in Hardware. July 18, Day 5 Memory. Instructor: Neil Rhodes. Software TLB Management

Memory Management. Chapter 4 Memory Management. Multiprogramming with Fixed Partitions. Ideally programmers want memory that is.

Page Replacement Chap 21, 22. Dongkun Shin, SKKU

Virtual Memory. Reading: Silberschatz chapter 10 Reading: Stallings. chapter 8 EEL 358

stack Two-dimensional logical addresses Fixed Allocation Binary Page Table

Outline. 1 Paging. 2 Eviction policies. 3 Thrashing 1 / 28

Chapter 8: Main Memory. Operating System Concepts 8th Edition

Memory Management Virtual Memory

Fall 2015 COMP Operating Systems. Lab #8

CS 333 Introduction to Operating Systems. Class 14 Page Replacement. Jonathan Walpole Computer Science Portland State University

CS 333 Introduction to Operating Systems. Class 14 Page Replacement. Jonathan Walpole Computer Science Portland State University

Virtual Memory Management

Transcription:

Page Replacement page 1

Page Replacement Algorithms Want lowest page-fault rate Evaluate algorithm by running it on a particular string of memory 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 page 2

Graph of Page Faults Versus The Number of Frames page 3

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) 1 1 4 5 2 2 1 3 9 page faults 4 frames 3 3 2 4 1 1 5 4 2 2 1 5 10 page faults 3 3 2 4 4 3 FIFO Replacement Belady s Anomaly more frames more page faults page 4

FIFO Page Replacement page 5

FIFO Illustrating Belady s Anomaly page 6

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, 5 1 4 2 6 page faults 3 4 5 How do you know this? Used for measuring how well your algorithm performs page 7

Optimal Page Replacement page 8

Least Recently Used (LRU) Algorithm Reference string: 1, 2, 3, 4, 1, 2, 5, 1, 2, 3, 4, 5 1 5 2 3 5 4 4 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 page 9

LRU Algorithm (Cont.) Stack implementation keep a stack of page numbers in a double link form: Page referenced: move it to the top requires 6 pointers to be changed Unlike counter based approach, does not search for replacement page 10

Use Of A Stack to Record The Most Recent Page References page 11

LRU Approximation Algorithms Reference bit With each page associate a bit, initially = 0 When page is referenced bit set to 1 Replace the one which is 0 (if one exists). We do not know the order, however. Additional reference bits Hardware sets bit, OS periodically shifts bit Second chance Need reference bit Clock replacement FIFO algorithm; if page to be replaced (in clock order) has reference bit = 1 then: set reference bit 0 leave page in memory replace next page (in clock order), subject to same rules page 12

Second-Chance (clock) Page-Replacement Algorithm Enhanced second-chance (reference & modified bit) page 13

Counting Algorithms Keep a counter of the number of references that have been made to each page LFU Algorithm: replaces page with smallest count. One problem is that pages that were active a long time back may survive. Can use a policy that shifts the counter periodically. MFU Algorithm: based on the argument that the page with the smallest count was probably just brought in and has yet to be used page 14

Page buffering algorithms Maintain a pool of free-frames If page needs to be written to disk, allocate a page from free pool, and once the write completes return that page to the free pool List of modified files and when idle, write contents to disk and reset modified bit Move pages to free-list, but if process needs that page again, move it from free to active list page 15

Allocation of Frames How should the OS distribute the frames among the various processes? Each process needs minimum number of pages - at least the minimum number of pages required for a single assembly instruction to complete Example: IBM 370 6 pages to handle SS MOVE instruction: instruction is 6 bytes, might span 2 pages 2 pages to handle from 2 pages to handle to Two major allocation schemes fixed allocation priority allocation page 16

Fixed Allocation Equal allocation For example, if there are 100 frames and 5 processes, give each process 20 frames. s S = " s a i i = size of process i m = total number of = allocation for p i p Proportional allocation Allocate according to the size of process m s s a a i 2 1 2 = 64 = 10 = 127 i frames si =! m S 10 = " 64! 5 137 127 = " 64! 59 137 page 17

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 page 18

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 It is possible for processes to suffer page faults through no fault of theirs However, improves system throughput Local replacement each process selects from only its own set of allocated frames May not use free space in the system page 19

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 because of low cpu utilization another process added to the system Thrashing a process is busy swapping pages in and out page 20

Thrashing (Cont.) page 21

Demand Paging and Thrashing Why does demand paging work? Locality model Process migrates from one locality to another Localities may overlap E.g. for ( ) { } computations; for (.. ) { } computations; Why does thrashing occur? Σ size of locality > total memory size page 22

Working-Set Model Δ working-set window a fixed number of page references Example: 10,000 instruction WSS i (working set of Process P i ) = total number of pages referenced in the most recent Δ (varies in time) if Δ too small will not encompass entire locality if Δ too large will encompass several localities if Δ = will encompass entire program D = Σ WSS i total demand frames if D > m Thrashing Policy if D > m, then suspend one of the processes page 23

Working-set model page 24

Keeping Track of the Working Set Approximate with interval timer + a reference bit Example: Δ = 10,000 Timer interrupts after every 5000 time units Keep in memory 2 bits for each page Whenever a timer interrupts copy and sets the values of all reference bits to 0 If one of the bits in memory = 1 page in working set Why is this not completely accurate? Improvement = 10 bits and interrupt every 1000 time units page 25

Page-Fault Frequency Scheme Establish acceptable page-fault rate If actual rate too low, process loses frame If actual rate too high, process gains frame page 26