CHAP7 - Memory Management Chapter 7 Memory Management...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Memory Management Chapter 7
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Memory Management Subdividing memory to accommodate multiple processes Memory needs to be allocated efficiently to pack as many processes into memory as possible
Background image of page 2
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
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 4
Memory Management Requirements Protection Processes should not be able to reference memory locations in another process without permission More importantly, processes should not access the portion of memory where the OS is resident 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
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
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
Background image of page 6
Memory Management Requirements Logical Organization Programs are written in modules Modules can be written and compiled independently Different degrees of protection given to modules (read-only, execute-only) Share modules
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Memory Management Requirements Physical Organization Memory available for a program plus its data may be insufficient Overlaying allows various modules to be assigned the same region of memory Programmer does not know how much space will be available
Background image of page 8
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
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 07/25/2008 for the course CSE 410 taught by Professor Bonakdarpour during the Summer '08 term at Michigan State University.

Page1 / 42

CHAP7 - Memory Management Chapter 7 Memory Management...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online