Memory Management. Memory

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

Chapter 9: Memory Management. Background

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

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

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

Chapter 8: Memory Management

Chapter 8: Main Memory

Chapter 8: Main Memory

Memory Management. Memory Management

Chapter 8: Memory Management Strategies

Module 9: Memory Management. Background. Binding of Instructions and Data to Memory

Module 8: Memory Management

Module 8: Memory Management

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

Logical versus Physical Address Space

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

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

Goals of Memory Management

CS307 Operating Systems Main Memory

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

Lecture 8 Memory Management Strategies (chapter 8)

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

CHAPTER 8: MEMORY MANAGEMENT. By I-Chen Lin Textbook: Operating System Concepts 9th Ed.

Chapter 8: Memory Management. Background Swapping Contiguous Allocation Paging Segmentation Segmentation with Paging

SHANDONG UNIVERSITY 1

Main Memory. CISC3595, Spring 2015 X. Zhang Fordham University

CS307: Operating Systems

CS 3733 Operating Systems:

Chapter 8: Memory-Management Strategies

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

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

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

Chapter 8: Memory- Management Strategies

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

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

Main Memory. Electrical and Computer Engineering Stephen Kim ECE/IUPUI RTOS & APPS 1

Main Memory Yi Shi Fall 2017 Xi an Jiaotong University

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

CHAPTER 8 - MEMORY MANAGEMENT STRATEGIES

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

Chapter 8: Memory Management. Operating System Concepts with Java 8 th Edition

Principles of Operating Systems

Chapter 8: Main Memory

Chapter 8 Memory Management

Chapter 8: Main Memory

Chapter 8 Main Memory

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

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

Chapter 8: Memory- Management Strategies Dr. Varin Chouvatut

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

CS3600 SYSTEMS AND NETWORKS

Memory Management. Minsoo Ryu. Real-Time Computing and Communications Lab. Hanyang University.

Memory Management Minsoo Ryu Real-Time Computing and Communications Lab. Hanyang University

Unit-03 Deadlock and Memory Management Unit-03/Lecture-01

Performance of Various Levels of Storage. Movement between levels of storage hierarchy can be explicit or implicit

Memory Management. Dr. Yingwu Zhu

Roadmap. Tevfik Koşar. CSC Operating Systems Spring Lecture - XII Main Memory - II. Louisiana State University

P r a t t hr h ee e : e M e M m e o m r o y y M a M n a a n g a e g m e e m n e t 8.1/72

Background. Contiguous Memory Allocation

Chapter 8 & Chapter 9 Main Memory & Virtual Memory

Introduction to Operating Systems

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

Page Table Structure. Hierarchical Paging. Hashed Page Tables. Inverted Page Tables

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

The Memory Management Unit. Operating Systems. Autumn CS4023

CS370 Operating Systems

CSE 421/521 - Operating Systems Fall Lecture - XII Main Memory Management. Tevfik Koşar. University at Buffalo. October 18 th, 2012.

Main Memory (Part II)

Memory Management. Dr. Yingwu Zhu

Memory Management and Protection

Main Memory (II) Operating Systems. Autumn CS4023

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

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

Basic Memory Management

CS370 Operating Systems

CS420: Operating Systems

Chapter 8: Memory Management

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

VII. Memory Management

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

Operating Systems. Memory Management. Lecture 9 Michael O Boyle

CS6401- Operating System UNIT-III STORAGE MANAGEMENT

Main Memory (Part I)

Chapter 9 Memory Management

Process. One or more threads of execution Resources required for execution

Fall 2015 COMP Operating Systems. Lab 06

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

Chapters 9 & 10: Memory Management and Virtual Memory

Operating System 1 (ECS-501)

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

Process. One or more threads of execution Resources required for execution. Memory (RAM) Others

Memory and multiprogramming

Process. Memory Management

CSE 4/521 Introduction to Operating Systems. Lecture 14 Main Memory III (Paging, Structure of Page Table) Summer 2018

COSC Operating Systems Design, Fall 2001, Byunggu Yu. Chapter 9 Memory Management (Lecture Note #8) 1. Background

Process. One or more threads of execution Resources required for execution. Memory (RAM) Others

Operating Systems Unit 6. Memory Management

Memory Management (2)

Introduction to Virtual Memory Management

Outline. V Computer Systems Organization II (Honors) (Introductory Operating Systems) Advantages of Multi-level Page Tables

Transcription:

Memory Management These slides are created by Dr. Huang of George Mason University. Students registered in Dr. Huang s courses at GMU can make a single machine readable copy and print a single copy of each slide for their own reference as long as the slide contains the copyright statement, and the GMU facilities are not used to produce the paper copies. Permission for any other use, either in machine-readable or printed form, must be obtained form the author in writing. CS471 1 Memory A a set of data entries indexed by addresses Typically the basic data unit is byte In 32 bit machines, 4 bytes grouped to words Have you seen those DRAM chips in your PC? 0000 0001 0002 0003 0004 0005 0006 0007 0008 0009 000A 000B 000C 000D 000E 000F CS471 2 1

Logical vs. Physical Address Space The addresses used by the RAM chips are called physical addresses. In primitive computing devices, the address a programmer/processor use is the actual address. When the process fetches byte 000A, the content of 000A is provided. CS471 3 In advanced computers, the processor operates in a separate address space, called logical address, or virtual address. A Memory Management Unit (MMU) is used to map logical addresses to physical addresses. Various mapping technologies to be discussed MMU is a hardware component Modern processors have their MMU on the chip (Pentium, Athlon, ) CS471 4 2

Continuous Mapping: Dynamic Relocation Virtual Memory Space Physical Memory Processor 4000 The processor want byte 0010, the 4010th byte is fetched CS471 5 MMU for Dynamic Relocation CS471 6 3

Segmented Mapping Virtual Memory Space Physical Memory Processor Obviously, more sophisticated MMU needed to implement this CS471 7 Swapping A process can be swapped temporarily out of memory to a backing store (a hard drive), and then brought back into memory for continued execution. Major part of swap time is transfer time; total transfer time is directly proportional to the amount of memory swapped. Modified versions of swapping are found on many systems, i.e., UNIX, Linux, and Windows. CS471 8 4

Schematic View of Swapping CS471 9 Contiguous Allocation Main memory usually into two partitions: Resident operating system, usually held in low memory with interrupt vector. User processes then held in high memory. Single-partition allocation Relocation register contains value of smallest physical address Limit register contains range of logical addresses each logical address must be less than the limit register. CS471 10 5

Hardware Support for Relocation and Limit Registers CS471 11 Contiguous Allocation (Cont.) Multiple-partition allocation Hole block of available memory; holes of various size are scattered throughout memory. When a process arrives, it is allocated memory from a hole large enough to accommodate it. OS OS OS OS process 5 process 5 process 5 process 5 process 9 process 9 process 8 process 10 process 2 process 2 process 2 process 2 CS471 12 6

Dynamic Storage Allocation Problem How to satisfy a request of size n from a list of free holes. First-fit: use the first hole big enough. Best-fit: use the smallest hole that is big enough must search entire list, unless ordered by size produces the smallest leftover hole CS471 13 Worst-fit: Allocate the largest hole must also search entire list produces the largest leftover hole First-fit and best-fit better than worst-fit in terms of speed and storage utilization. CS471 14 7

Compaction Must shuffle memory contents to place all free memory together in one large block. This is called compaction Compaction must be transparent to processes. This is achieved thru the relocation register. Must also coordinate with IO devices. CS471 15 Paging Divide physical memory into fixed-sized blocks called frames (size is power of 2, between 512 bytes and 8192 bytes). Divide logical memory into blocks of same size called pages. To run a program of size n pages, need to find n free frames and load program. Set up a page table to translate logical to physical addresses. CS471 16 8

Paging (Con t) Physical Memory Virtual Memory Frame 0 Page 0 Frame 1 Processor Page 1 Page 2 Frame 2 Frame 3 Page 3 Frame 4 Frame 5 Frame 6 CS471 17 Address Translation Scheme Address generated by CPU is divided into: Page number (p) used as an index into a page table which contains base address of each page in physical memory. Page offset (d) combined with base address to define the physical memory address that is sent to the memory unit. CS471 18 9

Address Translation Architecture CS471 19 Paging Example CS471 20 10

Paging Example CS471 21 Free Frames Before allocation After allocation CS471 22 11

Implementation of Page Table Page table is kept in main memory. Page-table base register (PTBR) points to the page table. Page-table length register (PRLR) indicates size of the page table. In this scheme every data/instruction access requires two memory accesses. One for the page table and one for the data/instruction. The two memory access problem can be solved by the use of a special fast-lookup hardware cache called associative memory or translation look-aside buffers (TLBs) CS471 23 Associative Memory Associative memory hardware parallel search Page # Frame # Address translation (A, A ) If A is in associative register, get frame # A out. Otherwise get frame # A from page table in memory CS471 24 12

Paging Hardware With TLB CS471 25 Effective Access Time Associative Lookup = ε time unit Assume memory cycle time is 1 microsecond Hit ratio percentage of times that a page number is found in the associative registers; ration related to number of associative registers. Hit ratio = α Effective Access Time (EAT) EAT = (1 + ε) α + (2 + ε)(1 α) = 2 + ε α CS471 26 13

Memory Protection with Paging Memory protection implemented by associating protection bit with each frame. Valid-invalid bit attached to each entry in the page table: valid indicates that the associated page is in the process logical address space, and is thus a legal page. invalid indicates that the page is not in the process logical address space. CS471 27 Valid (v) or Invalid (i) Bit In A Page Table CS471 28 14

Page Table Structure Hierarchical Paging Hashed Page Tables Inverted Page Tables CS471 29 Hierarchical Page Tables Break up the logical address space into multiple page tables. A simple technique is a two-level page table. CS471 30 15

Two-Level Paging Example A logical address (on 32-bit machine with 4K page size) is divided into: a page number consisting of 20 bits. a page offset consisting of 12 bits. Since the page table is paged, the page number is further divided into: a 10-bit page number. a 10-bit page offset. CS471 31 Thus, a logical address is as follows: Page number offset p 1 p 2 d 10 bit 10 bit 12 bit where p 1 is an index into the outer page table, and p 2 is the displacement within the page of the outer page table. CS471 32 16

Two-Level Page-Table Scheme CS471 33 Address-Translation Scheme Address-translation scheme for a two-level 32- bit paging architecture CS471 34 17

Hashed Page Tables Common in address spaces > 32 bits. The virtual page number is hashed into a page table. This page table contains a chain of elements hashing to the same location. Virtual page numbers are compared in this chain searching for a match. If a match is found, the corresponding physical frame is extracted. CS471 35 Hashed Page Table CS471 36 18

Inverted Page Table One entry for each real page of memory. Entry consists of the virtual address of the page stored in that real memory location, with information about the process that owns that page. Decreases memory needed to store each page table, but increases time needed to search the table when a page reference occurs. Use hash table to limit the search to one or at most a few page-table entries. CS471 37 Inverted Page Table Architecture CS471 38 19

Segmentation Memory-management scheme that supports user view of memory. A program is a collection of segments. A segment is a logical unit such as: main program, procedure/function, object, local variables, global variables, stack, symbol table, arrays CS471 39 User s View of a Program Global Data Stack Main() C++ Object Symbol table CS471 40 20

Logical View of Segmentation 1 1 4 2 3 4 2 3 user space physical memory space CS471 41 Segmentation Architecture Logical address consists of a two tuple: <segment-number, offset>, This addressing scheme has to be directly supported by the processor, such as all x86 processors. In x86 assembly programs, every address follows the above format. CS471 42 21

Segment table maps two-dimensional physical addresses; each table entry has: base contains the starting physical address where the segments reside in memory. limit specifies the length of the segment. Segment-table base register (STBR) points to the segment table s location in memory. Segment-table length register (STLR) indicates number of segments used by a program segment number s is legal if s < STLR. CS471 43 Segmentation Architecture (Cont.) Protection. With each entry in segment table associate: validation bit = 0 illegal segment read/write/execute privileges Protection bits associated with segments; code sharing occurs at segment level. CS471 44 22

Since segments vary in length, memory allocation is a dynamic storage-allocation problem. first fit/best fit A segmentation example is shown in the following diagram CS471 45 Segmentation Hardware CS471 46 23

Example of Segmentation CS471 47 Sharing of Segments CS471 48 24

Segmentation with Paging Virtual Address Physical Memory Space Frame 0 Frame 1 Seg 0 Page 0 Frame 2 Page 1 Frame 3 Page 2 Frame 4 Page 3 Frame 5 Seg 1 Page 0 Frame 6 Page 1 Frame 7 Seg 2 Page 0 Frame 8 Page 1 Frame 9 Page 2 Frame 10 Frame 11 Frame 12 Frame 13 CS471 49 Address Translation CS471 50 25

Case Study: Intel i386 MMU segmentation with paging two-level page table CS471 51 Intel 30386 Address Translation CS471 52 26