1 Memory Management Chapter 7. 2 Memory Management Subdividing memory to accommodate multiple processes Memory needs to be allocated to ensure a reasonable.

Slides:



Advertisements
Similar presentations
Chapters 7 & 8 Memory Management Operating Systems: Internals and Design Principles, 6/E William Stallings Patricia Roy Manatee Community College, Venice,
Advertisements

Part IV: Memory Management
Memory Management Chapter 7.
Fixed/Variable Partitioning
Memory Management Chapter 7. Memory Management Subdividing memory to accommodate multiple processes Memory needs to be allocated efficiently to pack as.
Memory Management Subdividing memory to accommodate multiple processes Memory needs to be allocated to ensure a reasonable supply of ready processes to.
Allocating Memory.
Chapter 7 Memory Management
Chapter 7 Memory Management Operating Systems: Internals and Design Principles, 6/E William Stallings Dave Bremer Otago Polytechnic, N.Z. ©2009, Prentice.
Memory Management. Managing Memory … The Simplest Case The O/S User Program 0 0xFFF … * Early PCs and Mainframes * Embedded Systems One user program at.
OS Fall’02 Memory Management Operating Systems Fall 2002.
Chapter 7 Memory Management
Memory Management Chapter 7. Memory Management Subdividing memory to accommodate multiple processes Memory needs to be allocated efficiently to pack as.
CSCI2413 Lecture 5 Operating Systems Memory Management 1 phones off (please)
Memory Management Chapter 7.
Memory Management Chapter 7 B.Ramamurthy. Memory Management Subdividing memory to accommodate multiple processes Memory needs to allocated efficiently.
1 Memory Management Chapter 7. 2 Memory Management Subdividing memory to accommodate multiple processes Memory needs to be allocated to ensure a reasonable.
Memory Management Chapter 5.
Memory Management Five Requirements for Memory Management to satisfy: –Relocation Users generally don’t know where they will be placed in main memory May.
1 Memory Management Memory Management Requirements –Relocation A programmer does not know in advance which other programs will be resident in main memory.
Chapter 7 Memory Management
1 Lecture 8: Memory Mangement Operating System I Spring 2008.
Chapter 91 Memory Management Chapter 9   Review of process from source to executable (linking, loading, addressing)   General discussion of memory.
1 Memory Management Chapter 7. 2 Roadmap n Memory management u Objectives u Requirements n Simple memory management u Memory partitioning F Fixed partitioning.
Chapter 7 Memory Management Seventh Edition William Stallings Operating Systems: Internals and Design Principles.
Operating System Chapter 7. Memory Management Lynn Choi School of Electrical Engineering.
Operating System 7 MEMORY MANAGEMENT. MEMORY MANAGEMENT REQUIREMENTS.
Memory Management Chapter 7.
Chapter 7 Memory Management Seventh Edition William Stallings Operating Systems: Internals and Design Principles.
1 Memory Management Memory Management COSC513 – Spring 2004 Student Name: Nan Qiao Student ID#: Professor: Dr. Morteza Anvari.
Memory Management Operating Systems: Internals and Design Principles, 6/E William Stallings Dave Bremer Otago Polytechnic, N.Z. ©2008, Prentice Hall Dr.
Chapter 7 Memory Management
Chapter 7 Memory Management Seventh Edition William Stallings Operating Systems: Internals and Design Principles.
CIS250 OPERATING SYSTEMS Memory Management Since we share memory, we need to manage it Memory manager only sees the address A program counter value indicates.
Memory Management Chapter 7.
Memory Management. Roadmap Basic requirements of Memory Management Memory Partitioning Basic blocks of memory management –Paging –Segmentation.
Subject: Operating System.
1 Memory Management Chapter 7. 2 Memory Management Subdividing memory to accommodate multiple processes Memory needs to be allocated to ensure a reasonable.
1 Memory Management Chapter 7. 2 Memory Management Subdividing memory to accommodate multiple processes Memory needs to be allocated to ensure a reasonable.
Main Memory. Chapter 8: Memory Management Background Swapping Contiguous Memory Allocation Paging Structure of the Page Table Segmentation Example: The.
1 Memory Management Chapter 8. 2 Memory Management n It is the task carried out by the OS and hardware to accommodate multiple processes in main memory.
Basic Memory Management 1. Readings r Silbershatz et al: chapters
Informationsteknologi Wednesday, October 3, 2007Computer Systems/Operating Systems - Class 121 Today’s class Memory management Virtual memory.
CS6502 Operating Systems - Dr. J. Garrido Memory Management – Part 1 Class Will Start Momentarily… Lecture 8b CS6502 Operating Systems Dr. Jose M. Garrido.
Memory management Ref: Stallings G.Anuradha. What is memory management? The task of subdivision of user portion of memory to accommodate multiple processes.
Memory Management Program must be brought (from disk) into memory and placed within a process for it to be run Main memory and registers are only storage.
CSNB224 – AAG 2007 Memory Management Chapter 7. CSNB224 – AAG 2007 Memory Management In uniprogramming system, memory is divided into two parts: for the.
Chapter 7 Memory Management Eighth Edition William Stallings Operating Systems: Internals and Design Principles.
Memory Management Chapter 5 Advanced Operating System.
1 Memory Management n In most schemes, the kernel occupies some fixed portion of main memory and the rest is shared by multiple processes.
2010INT Operating Systems, School of Information Technology, Griffith University – Gold Coast Copyright © William Stallings /2 Memory Management.
Chapter 8: Memory Management. 8.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 8: Memory Management Background Swapping Contiguous.
MEMORY MANAGEMENT. memory management  In a multiprogramming system, in order to share the processor, a number of processes must be kept in memory. 
COMP 3500 Introduction to Operating Systems Memory Management: Part 2 Dr. Xiao Qin Auburn University Slides.
Memory Management Chapter 7.
Chapter 7 Memory Management
Memory Management Chapter 7.
ITEC 202 Operating Systems
Requirements, Partitioning, paging, and segmentation
Day 19 Memory Management.
Chapter 8 Main Memory.
Main Memory Background Swapping Contiguous Allocation Paging
Memory Management Chapter 7.
Operating System Chapter 7. Memory Management
Operating Systems: Internals and Design Principles, 6/E
Chapter 7 Memory Management
Presentation transcript:

1 Memory Management Chapter 7

2 Memory Management Subdividing memory to accommodate multiple processes Memory needs to be allocated to ensure a reasonable supply of ready processes to consume available processor time

3 Memory Management Requirements Relocation –Programmer does not know where the program will be placed in memory when it is executed –While the program is executing, it may be swapped to disk and returned to main memory at a different location (relocated) –Memory references must be translated in the code to actual physical memory address

4 Memory Management Requirements Protection –Processes should not be able to reference memory locations in another process without permission –Impossible to check absolute addresses at compile time –Must be checked at run time –Memory protection requirement must be satisfied by the processor (hardware) rather than the operating system (software) Operating system cannot anticipate all of the memory references a program will make (Why?)

5 Registers Used during Execution Base register –Starting address for the process Bounds register –Ending location of the process These values are set when the process is loaded or when the process is swapped in Used to make sure programs stay within their bounds. Throws an interrupt if programs leave their bounds.

6 Registers Used during Execution The value of the base register is added to a relative address to produce an absolute address The resulting address is compared with the value in the bounds register If the address is not within bounds, an interrupt is generated to the operating system

7

8 Memory Management Requirements Protection (Additional Note) –Sharing Allow several processes to access the same portion of memory Better to allow each process access to the same copy of the program rather than have their own separate copy

9 Logical Organization Hardware more a linear ordering of bytes. –Problem: Programs are written in modules If the OS and Hardware view memory as modules –Allows modules to be written and compiled independently –Able to support different degrees of protection on modules (read-only, execute-only) –Able to share modules among processes (more human understandable)

10 Storing Stuff in Memory Partitions –More user understandable, relates back to programs better. –Keeps all code in a module together. Different Ways –Fixed –Dynamic –Buddy System

11 Fixed Partitioning Equal-size partitions –Any process whose size is less than or equal to the partition size can be loaded into an available partition. –If all partitions are full, the operating system can swap a process out of a partition. –(-) A program may not fit in a partition. The programmer must design the program with overlays.

12 Fixed Partitioning Main memory use is inefficient. Any program, no matter how small, occupies an entire partition. This is called internal fragmentation.

13

14 Placement Algorithm with Partitions Equal-size partitions –Because all partitions are of equal size, it does not matter which partition is used Unequal-size partitions –Can assign each process to the smallest partition within which it will fit –Queue for each partition –Processes are assigned in such a way as to minimize wasted memory within a partition

15

16 Dynamic Partitioning Partitions are of variable length and number Process is allocated exactly as much memory as required Eventually get holes in the memory. This is called external fragmentation Must use compaction to shift processes so they are contiguous and all free memory is in one block

17

18 Memory Compaction What things need to be taken into account when compacting memory? What would be the minimum cost to compact memory?

19 Dynamic Partitioning Placement Algorithm Operating system must decide which free block to allocate to a process Best-fit algorithm –Chooses the block that is closest in size to the request –Worst performer overall –Since smallest block is found for process, the smallest amount of fragmentation is left –Memory compaction must be done more often

20 Dynamic Partitioning Placement Algorithm First-fit algorithm –Scans memory form the beginning and chooses the first available block that is large enough –Fastest (assuming space in the front of memory) –May have many process loaded in the front end of memory that must be searched over when trying to find a free block

21 Dynamic Partitioning Placement Algorithm Next-fit –Scans memory from the location of the last placement –More often allocate a block of memory at the end of memory where the largest block is found –The largest block of memory is broken up into smaller blocks –Compaction is required to obtain a large block at the end of memory

22

23 Buddy System Entire space available is treated as a single block of 2 U If a request of size s such that 2 U-1 < s <= 2 U, entire block is allocated –Otherwise block is split into two equal buddies –Process continues until smallest block greater than or equal to s is generated

24 Relocation When program loaded into memory the actual (absolute) memory locations are determined A process may occupy different partitions which means different absolute memory locations during execution (from swapping)

25 Addresses Logical –Reference to a memory location independent of the current assignment of data to memory –Translation must be made to the physical address Relative –Address expressed as a location relative to some known point, but the point it’s relative to isn’t known until runtime. Physical –The absolute address or actual location in main memory

26

27 Why Partitioning Hard We want to keep program modules together. Dynamic sucks because of holes and needing to compact the memory Buddy system is decent but still potential to waste a large amount of memory if programs are a certain size.

28 Segmentation Partition memory into dynamic-size chunks and divide each process (module) into the chunk size available. –What is different from this over Partitions? All segments of all programs do not have to be of the same length. There is a maximum segment length Addressing consist of two parts - a segment number and an offset Since segments are not equal, segmentation is similar to dynamic partitioning

29

30

31 Segmentation External fragmentation instead of internal fragmentation. Difficult to do with hardware. Not used anymore due to hardware that allows paging to be more versatile. Usually visible to the programmer. –Allocating space for objects during run- time.

32 Paging Partition memory into small equal fixed-size chunks and divide each process into the same size chunks The chunks of a process are called pages and chunks of memory are called frames Operating system maintains a page table for each process –Contains the frame location for each page in the process –Memory address consists of a page number and offset within the page

33 Assignment of Process Pages to Free Frames

34 Note: Logical-to-physical address translation still done by hardware.

35 Page Tables for Example

36 Size of Pages Easiest to use a page size that is a power of 2. Logical addressing scheme is transparent to programmer, assembler, and linker. Easy to implement a hardware function to perform dynamic address translation.

37

38 End Note for Chapter 7 Programmer does not know how much space will be available when the program is run. –Virtual memory (Chapter 8) helps the OS deal with this problem.

39

40 Buddy System What’s the most memory that can be wasted in this system?

41