Академический Документы
Профессиональный Документы
Культура Документы
Operating System Concepts – 8th Edition 8.1 Silberschatz, Galvin and Gagne ©2009
Base and Limit Registers
A pair of base and limit registers define the logical
address space
For protection we need to make sure that each process
has a separate memory space, we need the ability to
determine the range of legal addresses that the process
may access and to ensure that the process can access
only these legal addresses.
We can provide this protection by using two registers,
usually a base and a limit
The base holds the smallest legal physical memory
address; the specifies the size of the range. For example,
if the base register holds 300040 and the limit register is
120900, then the program can legally access all
addresses from 300040 through 420939 (inclusive).
Operating System Concepts – 8th Edition 8.2 Silberschatz, Galvin and Gagne ©2009
Base and Limit Registers
A pair of base and limit registers define the logical address space
Base and limit registers are special hardware registers. When a
process is run, the base register is loaded with the physical location
where the process begins in memory. The limit register is loaded with
the length of the process. In other words, they define the logical
address space
Operating System Concepts – 8th Edition 8.3 Silberschatz, Galvin and Gagne ©2009
Base and Limit Registers
Operating System Concepts – 8th Edition 8.4 Silberschatz, Galvin and Gagne ©2009
Binding of Instructions and Data to Memory
A program resides on a disk as a binary executable file. To be
executed, the program must be brought into memory and placed
within a process.
Depending on the memory management in use, the process may be
moved between disk and memory during its execution. The
processes on the disk that are waiting to be brought into memory for
execution form the input queue
The normal procedure is to select one of the processes in the input
queue. As the process is executed, it accesses instructions and data
from memory.
Addresses in the source program are generally symbolic (such as
count). A compiler will typically bind these symbolic addresses to
relocatable addresses (such as "14 bytes from the beginning of this
module").
The linkage editor or loader will in turn bind the relocatable
addresses to absolute addresses (such as 74014). Each binding is a
mapping from one address space
Operating System Concepts – 8 Edition
th 8.5
to another. Silberschatz, Galvin and Gagne ©2009
Binding 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 changes. It refers to either the
operations performed by a compiler
Load time: Must generate relocatable code if memory
location is not known at compile time
Execution 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)
Operating System Concepts – 8th Edition 8.6 Silberschatz, Galvin and Gagne ©2009
Multistep Processing of a User Program
Operating System Concepts – 8th Edition 8.7 Silberschatz, Galvin and Gagne ©2009
Logical vs. Physical Address Space
In address translation process in MMU(memory management unit)
Logical address : generated by cpu.programmer concern with this
address.
Virtual address : reside in the hard disk , as a pages.
Physical address : reside in the RAM. It is the actual address.
Process
1: cpu generate the logical address and send it to the MMU.
2: MMU translate the logical address into the virtual address then
translate it to the physical address and send the physical address
to RAM.
3: when ever the RAM is full , the page which is not used rapidly is
returned to the hard disk , to allocate memory to the other
pages(processes).
Operating System Concepts – 8th Edition 8.8 Silberschatz, Galvin and Gagne ©2009
Logical vs. Physical Address Space
Operating System Concepts – 8th Edition 8.9 Silberschatz, Galvin and Gagne ©2009
Logical vs. Physical Address Space
Operating System Concepts – 8th Edition 8.10 Silberschatz, Galvin and Gagne ©2009
Memory-Management Unit (MMU)
1. A memory management unit (MMU), sometimes called paged memory
management unit (PMMU), is a computer hardware component responsible
for handling accesses to memory requested by the CPU. Its functions include
translation of virtual addresses to physical addresses (i.e., virtual memory
management), memory protection, and cache control.
2. Short for memory management unit, the hardware component that manages
virtual memory systems. Typically, the MMU is part of the CPU, though in
some designs it is a separate chip. The MMU includes a small amount of
memory that holds a table matching virtual addresses to physical addresses.
This table is called the Translation Look-aside Buffer (TLB). All requests for
data are sent to the MMU, which determines whether the data is in RAM or
needs to be fetched from the mass storage device. If the data is not in
memory, the MMU issues a page fault interrupt.
Operating System Concepts – 8th Edition 8.12 Silberschatz, Galvin and Gagne ©2009
Dynamic Loading
Routine is not loaded until it is called
Better memory-space utilization; unused routine is never
loaded
The main program is loaded into memory and is executed.
When a routine needs to call another routine, the calling
routine first checks to see whether the other routine has
been loaded. If it has not, the relocatable linking loader is
called to load the desired routine into memory and to
update the program's address tables to reflect this change.
Useful when large amounts of code are needed to handle
infrequently occurring cases
No special support from the operating system is required
implemented through program design
Operating System Concepts – 8th Edition 8.13 Silberschatz, Galvin and Gagne ©2009
Swapping
A process can be swapped temporarily out of memory to a
backing store, and then brought back into memory for continued
execution
Operating System Concepts – 8th Edition 8.15 Silberschatz, Galvin and Gagne ©2009
Schematic View of Swapping
Operating System Concepts – 8th Edition 8.16 Silberschatz, Galvin and Gagne ©2009
Contiguous Allocation
Contiguous memory allocation is a classical memory allocation model that assigns
a process consecutive memory blocks (that is, memory blocks having consecutive
addresses).
Contiguous allocation requires that each file occupy a set of contiguous blocks on
the disk
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 address
Limit register contains range of logical addresses – each logical address
must be less than the limit register
MMU maps logical address dynamically
Operating System Concepts – 8th Edition 8.18 Silberschatz, Galvin and Gagne ©2009
Contiguous Allocation (Cont)
Multiple-partition allocation
Hole – block of available memory; holes of various size
are scattered throughout memory
When a process arrives, it is allocated memory from a
hole large enough to accommodate it
Operating system maintains information about:
a) allocated partitions b) free partitions (hole)
OS OS OS OS
process 8 process 10
Operating System Concepts – 8th Edition 8.19 Silberschatz, Galvin and Gagne ©2009
Dynamic Storage-Allocation Problem
Operating System Concepts – 8th Edition 8.20 Silberschatz, Galvin and Gagne ©2009
Fragmentation
External Fragmentation – total memory space exists to satisfy a
request, but it is not contiguous
Internal Fragmentation – allocated memory may be slightly larger
than requested memory; this size difference is memory internal to a
partition, but not being used
Reduce external fragmentation by compaction
Shuffle memory contents to place all free memory together in
one large block
Compaction is possible only if relocation is dynamic, and is
done at execution time
I/O problem
Latch job in memory while it is involved in I/O
Do I/O only into OS buffers
Operating System Concepts – 8th Edition 8.21 Silberschatz, Galvin and Gagne ©2009
Paging
In computer operating systems, paging is one of the memory-management
schemes by which a computer can store and retrieve data from secondary
storage for use in main memory. In the paging memory-management
scheme, the operating system retrieves data from secondary storage in
same-size blocks called pages. The main advantage of paging over memory
segmentation is that it allows the physical address space of a process to be
non-contiguous. Before paging came into use, systems had to fit whole
programs into storage contiguously, which caused various storage and
fragmentation problems.
Logical address space of a process can be noncontiguous; process is
allocated physical memory whenever the latter is available
Divide 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 pages
Keep track of all free frames
To run a program of size n pages, need to find n free frames and load
program
Set up a page table to translate logical to physical addresses
Internal fragmentation Silberschatz, Galvin and Gagne ©2009
Operating System Concepts – 8th Edition 8.22
Paging
Operating System Concepts – 8th Edition 8.23 Silberschatz, Galvin and Gagne ©2009
Address Translation Scheme
Operating System Concepts – 8th Edition 8.24 Silberschatz, Galvin and Gagne ©2009
Paging Model of Logical and Physical Memory
Operating System Concepts – 8th Edition 8.25 Silberschatz, Galvin and Gagne ©2009
Paging Example
Operating System Concepts – 8th Edition 8.27 Silberschatz, Galvin and Gagne ©2009