Logical versus Physical Address Space

Similar documents
Module 8: Memory Management

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

Module 8: Memory Management

Chapter 9: Memory Management. Background

Chapter 8: Main Memory

Chapter 8: Main Memory

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

Chapter 8: Memory Management Strategies

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

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

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

Chapter 8: Memory Management

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

Memory Management. Memory Management

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

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

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

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

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

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

Chapter 8: Memory- Management Strategies

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 Strategies. Operating System Concepts 9 th Edition

Chapter 8: Memory-Management Strategies

CS307: Operating Systems

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

Principles of Operating Systems

Lecture 8 Memory Management Strategies (chapter 8)

Chapter 8: Main Memory

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

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

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

SHANDONG UNIVERSITY 1

CHAPTER 8 - MEMORY MANAGEMENT STRATEGIES

Chapter 8 Memory Management

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

Chapter 8: Main Memory

Memory Management. Memory

Goals of Memory Management

Background. Contiguous Memory Allocation

Main Memory Yi Shi Fall 2017 Xi an Jiaotong University

Chapter 8: Memory Management

Chapter 8: Memory- Management Strategies Dr. Varin Chouvatut

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

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

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

CS307 Operating Systems Main Memory

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

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

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

CS370 Operating Systems

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

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

CS 3733 Operating Systems:

Chapters 9 & 10: Memory Management and Virtual Memory

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

CS420: Operating Systems

Main Memory (Part I)

Chapter 8 Main Memory

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

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

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

Chapter 8 & Chapter 9 Main Memory & Virtual Memory

Chapter 9 Memory Management

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

Memory Management. Dr. Yingwu Zhu

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

Memory Management and Protection

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

CS6401- Operating System UNIT-III STORAGE MANAGEMENT

CS3600 SYSTEMS AND NETWORKS

Main Memory (II) Operating Systems. Autumn CS4023

The Memory Management Unit. Operating Systems. Autumn CS4023

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

Operating Systems. Memory Management. Lecture 9 Michael O Boyle

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

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

UNIT-III VIRTUAL MEMORY

Main Memory (Part II)

CS370 Operating Systems

CS 143A - Principles of Operating Systems

Memory Management. Dr. Yingwu Zhu

9.1 Background. In Chapter 6, we showed how the CPU can be shared by a set of processes. As a result of

Basic Memory Management

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

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

Operating System 1 (ECS-501)

Operating Systems Unit 6. Memory Management

CS420: Operating Systems. Paging and Page Tables

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

VII. Memory Management

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

Process. Memory Management

Memory Management (2)

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

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

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


Transcription:

CHAPTER 8: MEMORY MANAGEMENT Background Logical versus Physical Address Space Swapping Contiguous Allocation Paging Segmentation Segmentation with Paging Operating System Concepts, Addison-Wesley 1994 Silberschatz & Galvin 1994

Background Program must be brought into memory and placed within a process for it to be executed. Input queue collection of processes on the disk that are waiting to be brought into memory for execution. User programs go through several steps before being executed. Operating System Concepts, Addison-Wesley 1994 8.1 Silberschatz & Galvin 1994

Address binding of instructions and data to memory addresses can happen at three stages: Compile time: If memory location known a priori, absolute code can be generated; must recompile code if starting location changes. Load time: Must generate relocatable code if memory location is not known at compile time. Execution time: Binding delayed until run time if the process can be moved during its execution from one memory segment to another. Need hardware support for address maps (e.g., base and limit registers). Operating System Concepts, Addison-Wesley 1994 8.2 Silberschatz & Galvin 1994

Dynamic Loading routine is not loaded until it is called. - Better memory-space utilization; unused routine is never loaded. - Useful when large amounts of code are needed to handle infrequently occurring cases. - No special support from the operating system is required; implemented through program design. Dynamic Linking linking postponed until execution time. - Small piece of code, stub, used to locate the appropriate memory-resident library routine. - Stub replaces itself with the address of the routine, and executes the routine. - Operating system needed to check if routine is in processes memory address. Operating System Concepts, Addison-Wesley 1994 8.3 Silberschatz & Galvin 1994

Overlays keep in memory only those instructions and data that are needed at any given time. - Needed when process is larger than amount of memory allocated to it. - Implemented by user, no special support needed from operating system; programming design of overlay structure is complex. Operating System Concepts, Addison-Wesley 1994 8.4 Silberschatz & Galvin 1994

Logical versus Physical Address Space The concept of a logical address space that is bound to a separate physical address space is central to proper memory management. - Logical address generated by the CPU; also referred to as virtual address. - Physical address address seen by the memory unit. Logical and physical addresses are the same in compile-time and load-time address-binding schemes; logical (virtual) and physical addresses differ in execution-time address-binding scheme. Operating System Concepts, Addison-Wesley 1994 8.5 Silberschatz & Galvin 1994

Memory-management unit (MMU) hardware device that maps virtual to physical address. In MMU scheme, the value in the relocation register is added to every address generated by a user process at the time it is sent to memory. The user program deals with logical addresses; it never sees the real physical addresses. Operating System Concepts, Addison-Wesley 1994 8.6 Silberschatz & Galvin 1994

Swapping A process can be swapped temporarily out of memory to a backing store, and then brought back into memory for continued execution. Backing store fast disk large enough to accommodate copies of all memory images for all users; must provide direct access to these memory images. Roll out, roll in swapping variant used for priority-based scheduling algorithms; lowerpriority process is swapped out so higher-priority process can be loaded and executed. 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 and Microsoft Windows. Operating System Concepts, Addison-Wesley 1994 8.7 Silberschatz & Galvin 1994

Schematic view of swapping A memory A B disk B Operating System Concepts, Addison-Wesley 1994 8.8 Silberschatz & Galvin 1994

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 scheme used to protect user processes from each other, and from changing operating-system code and data. - 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. Operating System Concepts, Addison-Wesley 1994 8.9 Silberschatz & Galvin 1994

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. Example 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 Operating system maintains information about: - allocated partitions - free partitions (hole) Operating System Concepts, Addison-Wesley 1994 8.10 Silberschatz & Galvin 1994

Dynamic storage-allocation problem how to satisfy a request of size n from a list of free holes. - First-fit: Allocate the first hole that is big enough. - Best-fit: Allocate the smallest hole that is big enough; must search entire list, unless ordered by size. Produces the smallest leftover hole. - 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. Operating System Concepts, Addison-Wesley 1994 8.11 Silberschatz & Galvin 1994

External fragmentation total memory space exists to satisfy a request, but it is not contiguous. Internal fragmentation allocated memory may be slightly larger than requested memory; difference between these two numbers is memory internal to a partition, but not being used. Reduce external fragmentation by compaction. - Shuffle memory contents to place all free memory together in one large block. - Compaction is possible only if relocation is dynamic, and is done at execution time. - I/O problem Latch job in memory while it is involved in I/O. Do I/O only into OS buffers. Operating System Concepts, Addison-Wesley 1994 8.12 Silberschatz & Galvin 1994

Paging logical address space of a process can be noncontiguous; process is allocated physical memory wherever the latter is available. 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. Keep track of all free frames. 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. Internal fragmentation. Operating System Concepts, Addison-Wesley 1994 8.13 Silberschatz & Galvin 1994

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. CPU logical address p d f physical address d physical memory p f page table Operating System Concepts, Addison-Wesley 1994 8.14 Silberschatz & Galvin 1994

Separation between user s view of memory and actual physical memory reconciled by addresstranslation hardware; logical addresses are translated into physical addresses. frame number page 0 page 1 0 1 1 4 0 1 page 0 page 2 2 3 2 page 3 logical memory 3 7 page table 3 4 page 2 page 1 5 6 7 page 3 physical memory Operating System Concepts, Addison-Wesley 1994 8.15 Silberschatz & Galvin 1994

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 (PTLR) 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 registers or translation look-aside buffers (TLBs). Operating System Concepts, Addison-Wesley 1994 8.16 Silberschatz & Galvin 1994

Associative registers parallel search Page # Frame # Address translation (A, A ) - If A in associative register, get frame # out. - Otherwise get frame # from page table in memory. Hit ratio percentage of times that a page number is found in the associative registers; ratio related to number of associative registers. Effective Access Time (EAT) - associative lookup = ε time unit - memory cycle time - 1 microsecond - hit ratio = α EAT= (1 + ε) α +(2+ε)(1-α) =2+ε-α Operating System Concepts, Addison-Wesley 1994 8.17 Silberschatz & Galvin 1994

Memory protection implemented by associating protection bits 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. Operating System Concepts, Addison-Wesley 1994 8.18 Silberschatz & Galvin 1994

Multilevel Paging partitioning the page table allows the operating system to leave partitions unused until a process needs them. A two-level page-table scheme page 0 page 1... outer-page table 1. 500. 100. 708. 929. 900 page of page table page table page 100. page 500. page 708. page 900. page 929. memory Operating System Concepts, Addison-Wesley 1994 8.19 Silberschatz & Galvin 1994

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. Thus, a logical address is as follows: page number page offset p 1 p 2 d 10 10 12 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. Operating System Concepts, Addison-Wesley 1994 8.20 Silberschatz & Galvin 1994

Thus, a logical address is as follows: page number page offset p 1 p 2 d 10 10 12 Address-translation scheme for a two-level 32-bit paging architecture logical address p 1 p 2 d p 1 p 2 outer-page table page of page table d desired page Operating System Concepts, Addison-Wesley 1994 8.21 Silberschatz & Galvin 1994

Multilevel paging and performance - Since each level is stored as a separate table in memory, converting a logical address to a physical one may take four memory accesses. - Even though time needed for one memory access is quintupled, caching permits performance to remain reasonable. - Cache hit rate of 98 percent yields: effective access time = 0.98 120 + 0.02 520 = 128 nanoseconds which is only a 28 percent slowdown in memory access time. Operating System Concepts, Addison-Wesley 1994 8.22 Silberschatz & Galvin 1994

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. CPU logical address pid p d i physical address d physical memory search i pid p page table Operating System Concepts, Addison-Wesley 1994 8.23 Silberschatz & Galvin 1994

Shared pages One copy of read-only (reentrant) code shared among processes (i.e., text editors, compilers, window systems). ed 1 ed 2 ed 3 data 1 data 3 1 page table process P 1 for P 1 ed 1 ed 2 ed 3 3 4 6 3 4 6 2 page table process P 3 for P 3 ed 1 ed 2 ed 3 data 2 process P 2 3 4 6 7 page table for P 2 0 1 2 3 4 5 6 7 8 9 10 data 1 data 3 ed 1 ed 2 ed 3 data 2 Operating System Concepts, Addison-Wesley 1994 8.24 Silberschatz & Galvin 1994

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 local variables, global variables common block stack symbol table, arrays Example 1 1 4 3 2 4 2 3 user space physical memory Operating System Concepts, Addison-Wesley 1994 8.25 Silberschatz & Galvin 1994

Logical address consists of a two tuple: <segment-number, offset>. Segment table maps two-dimensional userdefined addresses into one-dimensional physical addresses; each entry of table 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. Operating System Concepts, Addison-Wesley 1994 8.26 Silberschatz & Galvin 1994

Relocation - dynamic - by segment table Sharing - shared segments - same segment number Protection With each entry in segment table associate: - validation bit = 0 illegal segment - read/write/execute privileges Allocation - first fit/best fit - external fragmentation Operating System Concepts, Addison-Wesley 1994 8.27 Silberschatz & Galvin 1994

Protection bits associated with segments; code sharing occurs at segment level. Since segments vary in length, memory allocation is a dynamic storage-allocation problem. editor segment 0 data 1 segment 1 0 1 limit 25286 4425 base 43062 68348 43062 editor logical memory process P 1 segment table process P 1 68348 72773 data 1 editor 98553 data 2 segment 0 data 1 segment 1 0 1 limit 25286 8850 base 43062 90003 physical memory logical memory segment table process P 2 process P 2 Operating System Concepts, Addison-Wesley 1994 8.28 Silberschatz & Galvin 1994

Segmentation with Paging The MULTICS system solved problems of external fragmentation and lengthy search times by paging the segments. logical address s d yes + segment length page table base no d p d STBR segment table trap memory + f f d physical address page table for segment s Solution differs from pure segmentation in that the segment-table entry contains not the base address of the segment, but rather the base address of a page table for this segment. Operating System Concepts, Addison-Wesley 1994 8.29 Silberschatz & Galvin 1994

The Intel 386 uses segmentation with paging for memory management, with a two-level paging scheme. logical address 16 selector 32 offset 0 descriptor table segment descriptor + linear address directory page offset page frame physical address page directory page table directory entry page table entry segment register Operating System Concepts, Addison-Wesley 1994 8.30 Silberschatz & Galvin 1994

Considerations in comparing memory-management strategies: Hardware support Performance Fragmentation Relocation Swapping Sharing Protection Operating System Concepts, Addison-Wesley 1994 8.31 Silberschatz & Galvin 1994

Operating System Concepts, Addison-Wesley 1994 Silberschatz & Galvin 1994