Professional Documents
Culture Documents
Memory Management: Early Systems
Memory Management: Early Systems
Memory Management:
Early Systems
• Disadvantages:
– Requires entire program to be stored contiguously
– Jobs are allocated space on the basis of first
available partition of required size
– Works well only if all of the jobs are of the same size
or if the sizes are known ahead of time
– Arbitrary partition sizes lead to undesired results
• Too small a partition size results in large jobs having
longer turnaround time
• Too large a partition size results in memory waste or
internal fragmentation
Figure 2.2 (continued): Main memory use during dynamic partition allocation
Table 2.9:
Table 2.10: Busy list after the job has released its memory.
The asterisk indicates the new null entry in the
busy list.
Table 2.11: Free list after the job has released its memory.
The asterisk indicates the new free block entry
replacing the null entry
Understanding Operating Systems, Fourth Edition 37
Relocatable Dynamic Partitions
• Compaction issues:
– What goes on behind the scenes when relocation
and compaction take place?
– What keeps track of how far each job has moved
from its original storage area?
– What lists have to be updated?