Core CS

logical vs Physical address space

A logical address space is the set of all virtual addresses generated by the CPU while a program executes, representing memory from the process's own perspective. In contrast, a physical address space is the set of actual physical memory locations (RAM) where code and data physically reside. The Memory Management Unit (MMU) translates logical addresses into physical addresses at runtime, allowing programs to execute seamlessly without needing to know or manage their exact hardware memory locations.

<h2>Definitions<ul><li>Logical Address Space: An abstract view of memory created by the operating system and CPU for a running program. The program treats this address range (typically starting at 0 up to a maximum limit) as its private, contiguous workspace. Because it does not directly touch physical RAM chips, it is also referred to as virtual memory.</li><li>Physical Address Space: The real, identifiable hardware memory locations available on the system’s RAM bus. Each physical address directly references a specific byte or word in main memory hardware.</li></ul>Key Differences & Characteristics<ul><li>Generation: Logical addresses are generated directly by the CPU during program compilation and runtime; physical addresses are accessed via memory buses on the physical RAM.</li><li>Hardware Intermediary: The Memory Management Unit (MMU) translates logical addresses into physical addresses at runtime using techniques like base/relocation registers, paging, or segmentation.</li><li>User Visibility: A programmer or process can directly view and work with logical addresses (e.g., pointers in C), but can never directly view or manipulate physical RAM addresses.</li><li>Size Independence: Logical address space can be larger or smaller than physical address space. With virtual memory, a 64-bit program can address far more logical space than the physical RAM installed.</li></ul><table><thead><tr><td>Feature</td><td>Logical Address Space</td><td>Physical Address Space</td></tr></thead><tbody><tr><td>Generated By</td><td>CPU</td><td>Memory Management Unit (MMU) / RAM hardware</td></tr><tr><td>Alternative Name</td><td>Virtual Address Space</td><td>Real / Absolute Address Space</td></tr><tr><td>Visibility</td><td>Directly accessible by user programs</td><td>Handled strictly by OS and hardware</td></tr><tr><td></td><td></td><td> </td></tr></tbody></table> Significance<ul><li>Process Isolation & Protection: Prevents a rogue or buggy process from overwriting another process's data or corrupting the operating system kernel.</li><li>Dynamic Relocation: Programs can be loaded into any available slot in physical memory or swapped to secondary storage without rewriting their internal memory references.</li><li>Efficient Memory Utilization: Physical memory does not need to be contiguous to hold a program; non-contiguous physical chunks (pages or frames) appear completely contiguous to the CPU.</li></ul>Advantages<ul><li>Multitasking Support: Multiple processes can share physical memory concurrently without stepping on each other.</li><li>Virtual Memory Expansion: Allows running programs whose memory footprint exceeds the capacity of available physical RAM.</li><li>Simplified Compiling: Compilers generate code assuming a standard starting address (e.g., $0x00000000$) rather than calculating actual RAM layouts.</li></ul>Disadvantages<ul><li>Translation Overhead: Every memory lookup requires an address translation step (via page tables or MMU registers), which can add latency (mitigated using TLBs).</li><li>Hardware Complexity: Requires dedicated MMU hardware and operating system structures (like page tables) that consume additional memory overhead.</li><li>Page Fault Handling: If a referenced logical address is swapped out to disk, handling the page fault incurs significant disk I/O delay.</li></ul></h2>