Chapter 8 Main Memory Operating System Concepts 8

  • Slides: 37
Download presentation
Chapter 8: Main Memory Operating System Concepts – 8 th Edition, Silberschatz, Galvin and

Chapter 8: Main Memory Operating System Concepts – 8 th Edition, Silberschatz, Galvin and Gagne © 2009

Chapter 8: Memory Management n Background n Swapping n Contiguous Memory Allocation n Paging

Chapter 8: Memory Management n Background n Swapping n Contiguous Memory Allocation n Paging n Structure of the Page Table n Segmentation n Example: The Intel Pentium Operating System Concepts – 8 th Edition 8. 2 Silberschatz, Galvin and Gagne © 2009

Objectives n To provide a detailed description of various ways of organizing memory hardware

Objectives n To provide a detailed description of various ways of organizing memory hardware n To discuss various memory-management techniques, including paging and segmentation Operating System Concepts – 8 th Edition 8. 3 Silberschatz, Galvin and Gagne © 2009

Base and Limit Registers n A pair of base and limit registers define the

Base and Limit Registers n A pair of base and limit registers define the logical address space Operating System Concepts – 8 th Edition 8. 4 Silberschatz, Galvin and Gagne © 2009

Binding of Instructions and Data to Memory n Address binding of instructions and data

Binding of Instructions and Data to Memory n Address binding of instructions and data to memory addresses can happen at three different stages l Compile time: If memory location known a priori, absolute code can be generated; must recompile code if starting location changes l Load time: Must generate relocatable code if memory location is not known at compile time l 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 – 8 th Edition 8. 5 Silberschatz, Galvin and Gagne © 2009

Logical vs. Physical Address Space n The concept of a logical address space that

Logical vs. Physical Address Space n The concept of a logical address space that is bound to a separate physical address space is central to proper memory management l Logical address – generated by the CPU; also referred to as virtual address l Physical address – address seen by the memory unit n 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 – 8 th Edition 8. 6 Silberschatz, Galvin and Gagne © 2009

Memory-Management Unit (MMU) n Hardware device that maps virtual to physical address n In

Memory-Management Unit (MMU) n Hardware device that maps virtual to physical address n 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 n The user program deals with logical addresses; it never sees the real physical addresses Operating System Concepts – 8 th Edition 8. 7 Silberschatz, Galvin and Gagne © 2009

Dynamic relocation using a relocation register Operating System Concepts – 8 th Edition 8.

Dynamic relocation using a relocation register Operating System Concepts – 8 th Edition 8. 8 Silberschatz, Galvin and Gagne © 2009

Swapping n A process can be swapped temporarily out of memory to a backing

Swapping n A process can be swapped temporarily out of memory to a backing store, and then brought back into memory for continued execution n Backing store – fast disk large enough to accommodate copies of all memory images for all users; must provide direct access to these memory images n Roll out, roll in – swapping variant used for priority-based scheduling algorithms; lower-priority process is swapped out so higher-priority process can be loaded and executed n 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) n System maintains a ready queue of ready-to-run processes which have memory images on disk n Operating System Concepts – 8 th Edition 8. 9 Silberschatz, Galvin and Gagne © 2009

Schematic View of Swapping Operating System Concepts – 8 th Edition 8. 10 Silberschatz,

Schematic View of Swapping Operating System Concepts – 8 th Edition 8. 10 Silberschatz, Galvin and Gagne © 2009

Contiguous Allocation n Main memory usually into two partitions: l Resident operating system, usually

Contiguous Allocation n Main memory usually into two partitions: l Resident operating system, usually held in low memory with interrupt vector l User processes then held in high memory n Relocation registers used to protect user processes from each other, and from changing operating-system code and data l Base register contains value of smallest physical address l Limit register contains range of logical addresses – each logical address must be less than the limit register l MMU maps logical address dynamically Operating System Concepts – 8 th Edition 8. 11 Silberschatz, Galvin and Gagne © 2009

Hardware Support for Relocation and Limit Registers Operating System Concepts – 8 th Edition

Hardware Support for Relocation and Limit Registers Operating System Concepts – 8 th Edition 8. 12 Silberschatz, Galvin and Gagne © 2009

Contiguous Allocation (Cont) n Multiple-partition allocation l Hole – block of available memory; holes

Contiguous Allocation (Cont) n Multiple-partition allocation l Hole – block of available memory; holes of various size are scattered throughout memory l When a process arrives, it is allocated memory from a hole large enough to accommodate it l Operating system maintains information about: a) allocated partitions b) free partitions (hole) OS OS process 5 process 9 process 8 process 2 Operating System Concepts – 8 th Edition process 10 process 2 8. 13 process 2 Silberschatz, Galvin and Gagne © 2009

Dynamic Storage-Allocation Problem How to satisfy a request of size n from a list

Dynamic Storage-Allocation Problem How to satisfy a request of size n from a list of free holes n First-fit: Allocate the first hole that is big enough n Best-fit: Allocate the smallest hole that is big enough; must search entire list, unless ordered by size l Produces the smallest leftover hole n Worst-fit: Allocate the largest hole; must also search entire list l Produces the largest leftover hole First-fit and best-fit better than worst-fit in terms of speed and storage utilization Operating System Concepts – 8 th Edition 8. 14 Silberschatz, Galvin and Gagne © 2009

Fragmentation n External Fragmentation – total memory space exists to satisfy a request, but

Fragmentation n External Fragmentation – total memory space exists to satisfy a request, but it is not contiguous n Internal Fragmentation – allocated memory may be slightly larger than requested memory; this size difference is memory internal to a partition, but not being used n Reduce external fragmentation by compaction l Shuffle memory contents to place all free memory together in one large block l Compaction is possible only if relocation is dynamic, and is done at execution time Operating System Concepts – 8 th Edition 8. 15 Silberschatz, Galvin and Gagne © 2009

Paging n Logical address space of a process can be noncontiguous; process is allocated

Paging n Logical address space of a process can be noncontiguous; process is allocated physical memory whenever the latter is available n Divide physical memory into fixed-sized blocks called frames (size is power of 2, between 512 bytes and 8, 192 bytes) n Divide logical memory into blocks of same size called pages n Keep track of all free frames n To run a program of size n pages, need to find n free frames and load program n Set up a page table to translate logical to physical addresses n Internal fragmentation Operating System Concepts – 8 th Edition 8. 16 Silberschatz, Galvin and Gagne © 2009

Address Translation Scheme n Address generated by CPU is divided into: l Page number

Address Translation Scheme n Address generated by CPU is divided into: l Page number (p) – used as an index into a page table which contains base address of each page in physical memory l Page offset (d) – combined with base address to define the physical memory address that is sent to the memory unit page number l page offset p d m-n n For given logical address space 2 m and page size 2 n Operating System Concepts – 8 th Edition 8. 17 Silberschatz, Galvin and Gagne © 2009

Paging Hardware Operating System Concepts – 8 th Edition 8. 18 Silberschatz, Galvin and

Paging Hardware Operating System Concepts – 8 th Edition 8. 18 Silberschatz, Galvin and Gagne © 2009

Paging Model of Logical and Physical Memory Operating System Concepts – 8 th Edition

Paging Model of Logical and Physical Memory Operating System Concepts – 8 th Edition 8. 19 Silberschatz, Galvin and Gagne © 2009

Paging Example 32 -byte memory and 4 -byte pages Operating System Concepts – 8

Paging Example 32 -byte memory and 4 -byte pages Operating System Concepts – 8 th Edition 8. 20 Silberschatz, Galvin and Gagne © 2009

Implementation of Page Table n Page table is kept in main memory n Page-table

Implementation of Page Table n Page table is kept in main memory n Page-table base register (PTBR) points to the page table n Page-table length register (PRLR) indicates size of the page table n In this scheme every data/instruction access requires two memory accesses. One for the page table and one for the data/instruction. n 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) Operating System Concepts – 8 th Edition 8. 21 Silberschatz, Galvin and Gagne © 2009

Associative Memory n Associative memory – parallel search Page # Frame # Address translation

Associative Memory n Associative memory – parallel search Page # Frame # Address translation (p, d) l If p is in associative register, get frame # out l Otherwise get frame # from page table in memory Operating System Concepts – 8 th Edition 8. 22 Silberschatz, Galvin and Gagne © 2009

Paging Hardware With TLB Operating System Concepts – 8 th Edition 8. 23 Silberschatz,

Paging Hardware With TLB Operating System Concepts – 8 th Edition 8. 23 Silberschatz, Galvin and Gagne © 2009

Effective Access Time n Associative Lookup = time unit n Assume memory cycle time

Effective Access Time n Associative Lookup = time unit n Assume memory cycle time is 1 microsecond n Hit ratio – percentage of times that a page number is found in the associative registers; ratio related to number of associative registers n Hit ratio = n Effective Access Time (EAT) EAT = (1 + ) + (2 + )(1 – ) =2+ – Operating System Concepts – 8 th Edition 8. 24 Silberschatz, Galvin and Gagne © 2009

Memory Protection n Memory protection implemented by associating protection bit with each frame n

Memory Protection n Memory protection implemented by associating protection bit with each frame n Valid-invalid bit attached to each entry in the page table: l “valid” indicates that the associated page is in the process’ logical address space, and is thus a legal page l “invalid” indicates that the page is not in the process’ logical address space Operating System Concepts – 8 th Edition 8. 25 Silberschatz, Galvin and Gagne © 2009

Valid (v) or Invalid (i) Bit In A Page Table Operating System Concepts –

Valid (v) or Invalid (i) Bit In A Page Table Operating System Concepts – 8 th Edition 8. 26 Silberschatz, Galvin and Gagne © 2009

Shared Pages n Shared code l One copy of read-only (reentrant) code shared among

Shared Pages n Shared code l One copy of read-only (reentrant) code shared among processes (i. e. , text editors, compilers, window systems). l Shared code must appear in same location in the logical address space of all processes n Private code and data l Each process keeps a separate copy of the code and data l The pages for the private code and data can appear anywhere in the logical address space Operating System Concepts – 8 th Edition 8. 27 Silberschatz, Galvin and Gagne © 2009

Shared Pages Example Operating System Concepts – 8 th Edition 8. 28 Silberschatz, Galvin

Shared Pages Example Operating System Concepts – 8 th Edition 8. 28 Silberschatz, Galvin and Gagne © 2009

Structure of the Page Table n Hierarchical Paging n Hashed Page Tables n Inverted

Structure of the Page Table n Hierarchical Paging n Hashed Page Tables n Inverted Page Tables Operating System Concepts – 8 th Edition 8. 29 Silberschatz, Galvin and Gagne © 2009

Hierarchical Page Tables n Break up the logical address space into multiple page tables

Hierarchical Page Tables n Break up the logical address space into multiple page tables n A simple technique is a two-level page table Operating System Concepts – 8 th Edition 8. 30 Silberschatz, Galvin and Gagne © 2009

Address-Translation Scheme Operating System Concepts – 8 th Edition 8. 31 Silberschatz, Galvin and

Address-Translation Scheme Operating System Concepts – 8 th Edition 8. 31 Silberschatz, Galvin and Gagne © 2009

Segmentation n Memory-management scheme that supports user view of memory n A program is

Segmentation n Memory-management scheme that supports user view of memory n A program is a collection of segments l A segment is a logical unit such as: main program procedure function method object local variables, global variables common block stack symbol table arrays Operating System Concepts – 8 th Edition 8. 32 Silberschatz, Galvin and Gagne © 2009

User’s View of a Program Operating System Concepts – 8 th Edition 8. 33

User’s View of a Program Operating System Concepts – 8 th Edition 8. 33 Silberschatz, Galvin and Gagne © 2009

Logical View of Segmentation 1 4 1 2 3 2 4 3 user space

Logical View of Segmentation 1 4 1 2 3 2 4 3 user space Operating System Concepts – 8 th Edition physical memory space 8. 34 Silberschatz, Galvin and Gagne © 2009

Segmentation Architecture n Logical address consists of a two tuple: <segment-number, offset>, n Segment

Segmentation Architecture n Logical address consists of a two tuple: <segment-number, offset>, n Segment table – maps two-dimensional physical addresses; each table entry has: l base – contains the starting physical address where the segments reside in memory l limit – specifies the length of the segment n Segment-table base register (STBR) points to the segment table’s location in memory n Segment-table length register (STLR) indicates number of segments used by a program; segment number s is legal if s < STLR Operating System Concepts – 8 th Edition 8. 35 Silberschatz, Galvin and Gagne © 2009

Segmentation Hardware Operating System Concepts – 8 th Edition 8. 36 Silberschatz, Galvin and

Segmentation Hardware Operating System Concepts – 8 th Edition 8. 36 Silberschatz, Galvin and Gagne © 2009

Example of Segmentation Operating System Concepts – 8 th Edition 8. 37 Silberschatz, Galvin

Example of Segmentation Operating System Concepts – 8 th Edition 8. 37 Silberschatz, Galvin and Gagne © 2009