Presentation is loading. Please wait.

Presentation is loading. Please wait.

Memory Management Chapter 7.

Similar presentations


Presentation on theme: "Memory Management Chapter 7."— Presentation transcript:

1 Memory Management Chapter 7

2 Memory Management Subdividing memory to accommodate multiple processes
Memory needs to be allocated efficiently to pack as many processes into memory as possible – to increase the cpu efficiency

3 Requirements Relocation Protection Sharing Logical organization
Physical organization

4 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

5

6 Memory Management Requirements
Protection – do not want interference Processes should not be able to reference memory locations in another process without permission Impossible to check absolute addresses in programs since the program could be relocated Must be checked during execution Operating system cannot anticipate all of the memory references a program will make Dynamic calculation of address Processor have to abort such instruction Software(o/s)?

7 Memory Management Requirements
Sharing Allow several processes to access the same portion of memory Better to allow each process (person) access to the same copy of the program rather than have their own separate copy Process cooperating through shared memory

8 Memory Management Requirements
Logical Organization Note : linear, sequence of bytes or words Programs are organized into modules Modules can be written and compiled independently Unmodifiable, modifiable Different degrees of protection given to modules (read-only, execute-only) References among modules will be resolved by the system at runtime Share modules Intuitively easy to understand

9 Memory Management Requirements
Physical Organization Main memory(volatile) and secondary memory; flow of information between MM and SM is major system concern Why? Memory available for a program plus its data may be insufficient Overlaying allows various modules to be assigned the same region of memory; impractical Programmer does not know how much space will be available and where that space will be

10 Memory partitioning Fixed partitioning Dynamic partitioning
Buddy system relocation

11

12 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

13 Fixed Partitioning Main memory use is inefficient. Any program, no matter how small, occupies an entire partition. This is called internal fragmentation. L(P) = 2M, yet use one 8M partition Alleviated by the unequal size partition

14 Placement Algorithm with Partitions
Equal-size partitions because all partitions are of equal size, it does not matter which partition is used If full, swap; which one? 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 Is it optimum?

15

16 Pro and cons Simple, minimal o/s s/w and processing overhead
Degree of multiprograming is limited Inefficient, esp. the size of P is not known VM or Overlaying Successful in early IBM mainframe - obsolete

17 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 – time consuming

18

19

20 Dynamic Partitioning Placement Algorithm
Operating system must decide which free block to allocate to a process (to minimize the compacting overhead) Best fit, first fit and next fit 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

21 Dynamic Partitioning Placement Algorithm
First-fit algorithm First available block that is large enough from the beginning Fastest, simplest May have many process loaded in the front end of memory that must be searched over when trying to find a free block

22 Dynamic Partitioning Placement Algorithm
Next-fit First available block that is large enough from the location of 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

23

24 Fixed partitioning limits the number of active processes & possibly inefficient memory utilization
Complex & overhead of compaction Compromise?!

25 Buddy System Entire space available is treated as a single block of 2U
Smallest size block = 2L Available memory block : 2k L <= k <= U If a request of size s such that 2U-1 < s <= 2U, 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 Maintain list of unallocation

26

27

28 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) Compaction will also cause a program to occupy a different partition which means different absolute memory locations How to solve this? Address scheme!

29 Addresses Logical Relative (offset) Physical
reference to a memory location independent of the current assignment of data to memory translation must be made to the physical address Relative (offset) address expressed as a location relative to some known point Physical the absolute address or actual location in main memory Need H/W to change r.addr to p.addr

30 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 and when the process is swapped in

31 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

32

33 Paging Partition memory into small equal-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 consist of a page number and offset within the page

34

35

36 Page Tables for Example

37 Fig 7.11 logical address Logical address page1 offset 478 Logical address Segment 1 offset 758 Relative address = 1502 user space

38 Segmentation 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

39 16bit = 6 bit (page) + 10 bit (offset
16bit physical address

40 16bit = 4 bit (segment) + 12 bit (offset
16bit physical address

41 summary Memory management Resource to be allocated, shared
Maintain as many process as possible Free programmer from physical constraints Paging & segmentation

42 What requirements are memory management intended to satisfy?
Relocation Protection Sharing

43 Why is the capability to relocate process desirable?
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) Compaction will also cause a program to occupy a different partition which means different absolute memory locations

44 Why is not possible to enforce memory protection at compile time?
Location of a program in MM is unpredictable Program language allows dynamic calculation of address at a runtime

45 What are some reasons to allow two or more processes to all have access to a particular region of memory? Share one copy of code by multiple processes Cooperation through the shared data

46 In a fixed partition scheme, what are the advantages of using unequal-size partitioning?
Minimize internal fragmentation Can serve relatively lager size process

47 What is the difference between internal and external fragmentations?

48 What are the distinction among logical, relative, and physical addresses?

49 What is the difference between a page and a frame

50 What is the difference between a page and a fragment?

51 For dynamic partitioning, a list of free blocks of memory should be maintained. For each of three methods discussed( best, first, next-fit), what is the average length of search?

52 The Fibonacci sequence is defined as follows:
F0 = 0, F1 = 1 Fn+2 = Fn+1 + Fn Could this sequence to be used to established a buddy system? What would be advantage of this system over the binary buddy system described in this chapter?


Download ppt "Memory Management Chapter 7."

Similar presentations


Ads by Google