Virtual Memory. control structures and hardware support

Similar documents
Chapter 8 Virtual Memory

Chapter 8 Virtual Memory

Memory Management Virtual Memory

ECE519 Advanced Operating Systems

a process may be swapped in and out of main memory such that it occupies different regions

Virtual to physical address translation

MEMORY MANAGEMENT/1 CS 409, FALL 2013

Chapter 8 Virtual Memory

Virtual Memory. Chapter 8

Operating Systems CSE 410, Spring Virtual Memory. Stephen Wagner Michigan State University

CSCI 4717 Computer Architecture. Memory Management. What is Swapping? Swapping. Partitioning. Fixed-Sized Partitions (continued)

Objectives and Functions Convenience. William Stallings Computer Organization and Architecture 7 th Edition. Efficiency

PROCESS VIRTUAL MEMORY. CS124 Operating Systems Winter , Lecture 18

Operating System Support

Chapter 8. Operating System Support. Yonsei University

COMP 346 WINTER 2018 MEMORY MANAGEMENT (VIRTUAL MEMORY)

Memory Management. Reading: Silberschatz chapter 9 Reading: Stallings. chapter 7 EEL 358

Operating Systems: Internals and Design Principles. Chapter 7 Memory Management Seventh Edition William Stallings

Memory and multiprogramming

CPE300: Digital System Architecture and Design

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

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

Multi-Process Systems: Memory (2) Memory & paging structures: free frames. Memory & paging structures. Physical memory

Chapter 8: Main Memory

Memory Management Virtual Memory

Chapter 8: Main Memory

8.1 Background. Part Four - Memory Management. Chapter 8: Memory-Management Management Strategies. Chapter 8: Memory Management

Virtual Memory. Chapter 8

Chapter 8 Memory Management

Part Three - Memory Management. Chapter 8: Memory-Management Strategies

Chapter 8: Memory Management Strategies

SMD149 - Operating Systems - Memory

Operating Systems Lecture 6: Memory Management II

Operating Systems. 09. Memory Management Part 1. Paul Krzyzanowski. Rutgers University. Spring 2015

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

Basic Memory Management. Basic Memory Management. Address Binding. Running a user program. Operating Systems 10/14/2018 CSC 256/456 1

I.-C. Lin, Assistant Professor. Textbook: Operating System Concepts 8ed CHAPTER 8: MEMORY

Chapter 8. Virtual Memory

Memory Management. Memory Management

Agenda. CS 61C: Great Ideas in Computer Architecture. Virtual Memory II. Goals of Virtual Memory. Memory Hierarchy Requirements

Memory Management Cache Base and Limit Registers base limit Binding of Instructions and Data to Memory Compile time absolute code Load time

CS307 Operating Systems Main Memory

The memory of a program. Paging and Virtual Memory. Swapping. Paging. Physical to logical address mapping. Memory management: Review

Memory Management. Dr. Yingwu Zhu

Memory Management. Contents: Memory Management. How to generate code? Background

Memory: Page Table Structure. CSSE 332 Operating Systems Rose-Hulman Institute of Technology

CSE 120 Principles of Operating Systems Spring 2017

Recap: Memory Management

VIRTUAL MEMORY II. Jo, Heeseung

Memory Management. An expensive way to run multiple processes: Swapping. CPSC 410/611 : Operating Systems. Memory Management: Paging / Segmentation 1

Background Swapping Contiguous Memory Allocation Paging Structure of the Page Table Segmentation

I.-C. Lin, Assistant Professor. Textbook: Operating System Principles 7ed CHAPTER 8: MEMORY

CPS104 Computer Organization and Programming Lecture 16: Virtual Memory. Robert Wagner

Chapter 8 Main Memory

Lecture 9: Virtual Memory

CPS 104 Computer Organization and Programming Lecture 20: Virtual Memory

Virtual Memory: Mechanisms. CS439: Principles of Computer Systems February 28, 2018

Chapter 9: Memory Management. Background

Memory management. Requirements. Relocation: program loading. Terms. Relocation. Protection. Sharing. Logical organization. Physical organization

Process size is independent of the main memory present in the system.

CS 153 Design of Operating Systems Winter 2016

File Systems. OS Overview I/O. Swap. Management. Operations CPU. Hard Drive. Management. Memory. Hard Drive. CSI3131 Topics. Structure.

Outlook. Background Swapping Contiguous Memory Allocation Paging Structure of the Page Table Segmentation Example: The Intel Pentium

CSE 120 Principles of Operating Systems

ECE 341. Lecture # 18

Chapter 8: Memory Management

Chapter 8 & Chapter 9 Main Memory & Virtual Memory

CS307: Operating Systems

Address spaces and memory management

Basic Memory Management

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

Topics: Memory Management (SGG, Chapter 08) 8.1, 8.2, 8.3, 8.5, 8.6 CS 3733 Operating Systems

Chapter 3 - Memory Management

CS 3733 Operating Systems:

6 - Main Memory EECE 315 (101) ECE UBC 2013 W2

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

Operating Systems. Operating Systems Sina Meraji U of T

Operating Systems Unit 6. Memory Management

CS 318 Principles of Operating Systems

CS399 New Beginnings. Jonathan Walpole

16 Sharing Main Memory Segmentation and Paging

Operating System Support

Chapter 8: Memory- Manage g me m nt n S tra r t a e t gie i s

Address Translation. Jinkyu Jeong Computer Systems Laboratory Sungkyunkwan University

Virtual Memory Overview

Chapter 8: Memory-Management Strategies

Operating Systems. Paging... Memory Management 2 Overview. Lecture 6 Memory management 2. Paging (contd.)

Operating Systems. Designed and Presented by Dr. Ayman Elshenawy Elsefy

INSTITUTO SUPERIOR TÉCNICO. Architectures for Embedded Computing

Memory Management. Goals of Memory Management. Mechanism. Policies

Memory Management. Memory

CHAPTER 8 - MEMORY MANAGEMENT STRATEGIES

EECS 482 Introduction to Operating Systems

CSE 4/521 Introduction to Operating Systems. Lecture 27 (Final Exam Review) Summer 2018

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

Memory management. Last modified: Adaptation of Silberschatz, Galvin, Gagne slides for the textbook Applied Operating Systems Concepts

Chapter 9 Memory Management Main Memory Operating system concepts. Sixth Edition. Silberschatz, Galvin, and Gagne 8.1

Chapter 7 Memory Management

Chapter 8: Main Memory

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

Transcription:

Virtual Memory control structures and hardware support 1

Hardware and Control Structures Memory references are dynamically translated into physical addresses at run time A process may be swapped in and out of main memory such that it occupies different regions A process may be broken up into pieces that do not need to located contiguously in main memory Not necessarily all pieces of a process need to be loaded in main memory during execution 2

Execution of a Program Operating system brings into main memory a few pieces of the program Resident set - portion of process that is in main memory An interrupt is generated when an address is needed that is not in main memory (page fault) Operating system places the process in a blocking state the process is waiting its page from disk this is equivalent to a blocking I/O request 3

Execution of a Program Piece of process that contains the logical address is brought into main memory Operating system issues a disk I/O Read request Another process is dispatched to run while the disk I/O takes place An interrupt is issued when disk I/O complete which causes the operating system to place the affected process in the Ready state 4

Advantages of Breaking up a Process More processes may be maintained in main memory Only load in some of the pieces of each process With so many processes in main memory, it is very likely a process will be in the Ready state at any particular time A process may be larger than all of main memory 5

Thrashing Swapping out a piece of a process just before that piece is needed if this happens frequently a lot of I/O is needed at the extreme point all processes are waiting for their pages from the disk The processor spends most of its time swapping pieces rather than executing user instructions 6

Principle of Locality 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 7

principle of locality

Support Needed for Virtual Memory Hardware must support paging and segmentation Operating system must be able to manage the movement of pages and/or segments between secondary memory and main memory 9

paging and virtual memory Each process has its own page table Each page table entry contains the frame number of the corresponding page in main memory An additional bit is needed to indicate whether the page is in main memory or not 10

Modify Bit in Page Table Modify bit is needed to indicate if the page has been altered since it was last loaded into main memory If no change has been made, the page does not have to be written to the disk when it needs to be swapped out 11

Paging 12

address translation for paging 13

very big page tables what if a process use a limited number of small parts of the page table? other parts may be not used at the moment or not used at all a lot of memory wasted for unused page table entries page tables should treated largely as part of the process image hierarchical page tables, inverted page tables 14

Two-Level Scheme for 32-bit Address (pentium like) 15

address translation in a two-level schema 16

Inverted Page Table one table and one entry for each frame regardless of the number of processes Page number portion of a virtual address is mapped into a hash value Hash value points to inverted page table collisions are solved by chaining Used on PowerPC, UltraSPARC, and IA- 64 architecture 17

inverted page table - 18

Translation Lookaside Buffer Each virtual memory reference can cause two physical memory accesses One to fetch the page table entry One to read/write the data To overcome this problem a highspeed cache is set up for page table entries Called a Translation Lookaside Buffer (TLB) 19

Translation Lookaside Buffer Contains page table entries that have been most recently used it performs an associative mapping between page numbers and page table entries 20

Translation Lookaside Buffer Given a virtual address, processor examines the TLB If page table entry is present (TLB hit), the frame number is retrieved and the real address is formed If page table entry is not found in the TLB (TLB miss), the page number is used to index the process page table 21

Translation Lookaside Buffer if page is already in main memory the TLB is updated to include the new page entry If not in main memory a page fault is issued OS is called 22

address translation with TLB 23

lookup algorithm for virutal memory paging with TLB

direct vs. associative mapping 25

TLB and regular cache 26

Page Size Smaller page size, less amount of internal fragmentation Smaller page size, more pages required per process More pages per process means larger page tables Larger page tables means large portion of page tables in virtual memory Secondary memory is designed to efficiently transfer large blocks of data so a large page size is better 27

Page Size Small page size, large number of pages will be found in main memory As time goes on during execution, the pages in memory will all contain portions of the process near recent references. Page faults low. Increased page size causes pages to contain locations further from any recent reference. Page faults rise. 28

typical paging behavior typical anomalous 29

Example Page Sizes 30

Segmentation Segments may have be unequal size segment size may dynamically increase may simplify handling of growing data structures Allows modules of programs to be altered and recompiled independently makes easy to share data among processes implements protection mechanisms 31

Segment Tables one entry for each segment of the process each entry contains base address for the segment in main memory the length of the segment A bit is needed to determine if segment is already in main memory Another bit is needed to determine if the segment has been modified since it was loaded in main memory 32

Segment Table Entries 33

address translation for segmentation 34

Combined Paging and Segmentation Paging is transparent to the programmer Segmentation is visible to the programmer Each segment is broken into fixedsize pages 35

Combined Segmentation and Paging 36

address translation for segmentation/paging systems 37