chapter 8: main memory - universitas diponegororizal.blog.undip.ac.id/files/2009/09/ch81.pdf ·...

Chapter 8: Main MemoryChapter 8: Main Memory

8.2 Silberschatz, Galvin and Gagne ©2005Operating System Concepts – 7th Edition, Feb 22, 2005

Chapter 8: Memory ManagementChapter 8: Memory Management

BackgroundSwapping Contiguous Memory AllocationPagingStructure of the Page TableSegmentationExample: The Intel Pentium


ObjectivesObjectives

To provide a detailed description of various ways of organizing memory hardwareTo discuss various memory-management techniques, including paging and segmentationTo provide a detailed description of the Intel Pentium, which supports both pure segmentation and segmentation with paging


BackgroundBackground

Program must be brought (from disk) into memory and placed within a process for it to be runMain memory and registers are only storage CPU can access directlyRegister access in one CPU clock (or less)Main memory can take many cyclesCache sits between main memory and CPU registersProtection of memory required to ensure correct operation


Base and Limit RegistersBase and Limit Registers

A pair of base and limit registers define the logical address space


Binding of Instructions and Data to MemoryBinding of Instructions and Data to Memory

Address binding of instructions and data to memory addresses can happen at three different stages

Compile time: If memory location known a priori, absolute code can be generated; must recompile code if starting location changesLoad time: Must generate relocatable code if memory location is not known at compile timeExecution 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)


MultistepMultistep Processing of a User Program Processing of a User Program


Logical vs. Physical Address SpaceLogical vs. 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 addressPhysical 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


MemoryMemory--Management Unit (Management Unit (MMUMMU))

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


Dynamic relocation using a relocation registerDynamic relocation using a relocation register


Dynamic LoadingDynamic Loading

Routine is not loaded until it is calledBetter memory-space utilization; unused routine is never loadedUseful when large amounts of code are needed to handle infrequently occurring casesNo special support from the operating system is required implemented through program design


Dynamic LinkingDynamic Linking

Linking postponed until execution timeSmall piece of code, stub, used to locate the appropriate memory-resident library routineStub replaces itself with the address of the routine, and executes the routineOperating system needed to check if routine is in processes’memory addressDynamic linking is particularly useful for librariesSystem also known as shared libraries


SwappingSwapping

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; lower-priority 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, Linux, and Windows)System maintains a ready queue of ready-to-run processes which have memory images on disk


Schematic View of SwappingSchematic View of Swapping


Contiguous AllocationContiguous Allocation

Main memory usually into two partitions:Resident operating system, usually held in low memory with interrupt vectorUser processes then held in high memory

Relocation registers used to protect user processes from each other, and from changing operating-system code and data

Base register contains value of smallest physical addressLimit register contains range of logical addresses – each logical address must be less than the limit register MMU maps logical address dynamically


HW address protection with base and limit registersHW address protection with base and limit registers


Contiguous Allocation (Cont.)Contiguous Allocation (Cont.)

Multiple-partition allocationHole – block of available memory; holes of various size are scattered throughout memoryWhen a process arrives, it is allocated memory from a hole large enough to accommodate itOperating system maintains information about:a) allocated partitions b) free partitions (hole)

OS

process 5

process 8

process 2

OS

process 5

process 2

OS

process 5

process 2

OS

process 5

process 9

process 2

process 9

process 10


Dynamic StorageDynamic Storage--Allocation ProblemAllocation Problem

First-fit: Allocate the first hole that is big enoughBest-fit: Allocate the smallest hole that is big enough; must search entire list, unless ordered by size

Produces the smallest leftover holeWorst-fit: Allocate the largest hole; must also search entire list

Produces the largest leftover hole

How to satisfy a request of size n from a list of free holes

First-fit and best-fit better than worst-fit in terms of speed and storage utilization


FragmentationFragmentation

External Fragmentation – total memory space exists to satisfy a request, but it is not contiguousInternal Fragmentation – allocated memory may be slightly larger than requested memory; this size difference is memory internal to a partition, but not being usedReduce external fragmentation by compaction

Shuffle memory contents to place all free memory together in one large blockCompaction is possible only if relocation is dynamic, and is done at execution timeI/O problem

Latch job in memory while it is involved in I/ODo I/O only into OS buffers


PagingPaging

Logical address space of a process can be noncontiguous; process is allocated physical memory whenever the latter is availableDivide physical memory into fixed-sized blocks called frames(size is power of 2, between 512 bytes and 8,192 bytes)Divide logical memory into blocks of same size called pagesKeep track of all free framesTo run a program of size n pages, need to find n free frames and load programSet up a page table to translate logical to physical addressesInternal fragmentation


Address Translation SchemeAddress 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

For given logical address space 2m and page size 2n

page number page offset

p d

m - n n


Paging HardwarePaging Hardware


Paging Model of Logical and Physical MemoryPaging Model of Logical and Physical Memory


Paging ExamplePaging Example

32-byte memory and 4-byte pages


Free FramesFree Frames

Before allocation After allocation


Implementation of Page TableImplementation of Page Table

Page table is kept in main memoryPage-table base register (PTBR) points to the page tablePage-table length register (PRLR) indicates size of the page tableIn 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)Some TLBs store address-space identifiers (ASIDs) in each TLB entry – uniquely identifies each process to provide address-space protection for that process


Associative MemoryAssociative Memory

Associative memory – parallel search

Address translation (p, d)If p is in associative register, get frame # outOtherwise get frame # from page table in memory

Page # Frame #


Paging Hardware With TLBPaging Hardware With TLB


Effective Access TimeEffective Access Time

Associative Lookup = ε time unitAssume memory cycle time is 1 microsecondHit ratio – percentage of times that a page number is found in the associative registers; ratio related to number of associative registersHit ratio = αEffective Access Time (EAT)

EAT = (1 + ε) α + (2 + ε)(1 – α)= 2 + ε – α


Memory ProtectionMemory Protection

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


Valid (v) or Invalid (i) Bit In A Page TableValid (v) or Invalid (i) Bit In A Page Table


Shared PagesShared Pages

Shared codeOne copy of read-only (reentrant) code shared among processes (i.e., text editors, compilers, window systems).Shared code must appear in same location in the logical address space of all processes

Private code and dataEach process keeps a separate copy of the code and dataThe pages for the private code and data can appear anywhere in the logical address space


Shared Pages ExampleShared Pages Example


Structure of the Page TableStructure of the Page Table

Hierarchical Paging

Hashed Page Tables

Inverted Page Tables


Hierarchical Page TablesHierarchical Page Tables

Break up the logical address space into multiple page tables

A simple technique is a two-level page table


TwoTwo--Level PageLevel Page--Table SchemeTable Scheme


TwoTwo--Level Paging ExampleLevel Paging Example

A logical address (on 32-bit machine with 1K page size) is divided into:a page number consisting of 22 bitsa page offset consisting of 10 bits

Since the page table is paged, the page number is further divided into:a 12-bit page number a 10-bit page offset

Thus, a logical address is as follows:

where pi is an index into the outer page table, and p2 is the displacement within the page of the outer page table

page number page offset

pi p2 d

12 10 10


AddressAddress--Translation SchemeTranslation Scheme


ThreeThree--level Paging Schemelevel Paging Scheme


Hashed Page TablesHashed 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.


Hashed Page TableHashed Page Table


Inverted Page TableInverted Page Table

One entry for each real page of memoryEntry consists of the virtual address of the page stored in that real memory location, with information about the process that owns that pageDecreases memory needed to store each page table, but increases time needed to search the table when a page reference occursUse hash table to limit the search to one — or at most a few — page-table entries


Inverted Page Table ArchitectureInverted Page Table Architecture


SegmentationSegmentation

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,method,object,local variables, global variables,common block,stack,symbol table, arrays


UserUser’’s View of a Programs View of a Program


Logical View of SegmentationLogical View of Segmentation

1

3

2

4

1

4

2

3

user space physical memory space


Segmentation Architecture Segmentation Architecture

Logical address consists of a two tuple:<segment-number, offset>,

Segment table – maps two-dimensional physical addresses; each table entry has:

base – contains the starting physical address where the segments reside in memorylimit – specifies the length of the segment

Segment-table base register (STBR) points to the segment table’s location in memorySegment-table length register (STLR) indicates number of segments used by a program;

segment number s is legal if s < STLR


Segmentation Architecture (Cont.)Segmentation Architecture (Cont.)

ProtectionWith each entry in segment table associate:

validation bit = 0 ⇒ illegal segmentread/write/execute privileges

Protection bits associated with segments; code sharing occurs at segment levelSince segments vary in length, memory allocation is a dynamic storage-allocation problemA segmentation example is shown in the following diagram


Segmentation HardwareSegmentation Hardware


Example of SegmentationExample of Segmentation


Example: The Intel PentiumExample: The Intel Pentium

Supports both segmentation and segmentation with pagingCPU generates logical address

Given to segmentation unitWhich produces linear addresses

Linear address given to paging unitWhich generates physical address in main memoryPaging units form equivalent of MMU


Logical to Physical Address Translation in Logical to Physical Address Translation in PentiumPentium


Intel Pentium SegmentationIntel Pentium Segmentation


Pentium Paging ArchitecturePentium Paging Architecture


Linear Address in LinuxLinear Address in Linux

Broken into four parts:


ThreeThree--level Paging in Linuxlevel Paging in Linux

End of Chapter 8End of Chapter 8

chapter 8: main memory - universitas diponegororizal.blog.undip.ac.id/files/2009/09/ch81.pdf ·...

Documents