Core CS

Virtual Memory

Virtual Memory is a memory management technique that creates an illusion of a very large main memory by combining physical RAM with secondary storage (like an SSD or hard drive). It allows a computer to execute programs larger than its installed RAM by loading only active chunks of code into memory while temporarily parking idle data on the disk.

<h2>Definition & Key Points Virtual memory maps the virtual addresses used by an application onto physical addresses in computer memory. The operating system handles this translation automatically via dedicated hardware called the Memory Management Unit (MMU).<ul><li><img src="https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcTi6Yrl7gH_nsRNnIguzPcU-YDNXIRxySnTOfUUbG-u4ubT-wUt_VccDPp2&s=10" alt="Virtual memory mapping via page table, AI generated">Pages and Frames: Virtual address space is divided into fixed-size blocks called pages, while physical RAM is divided into matching blocks called page frames.</li><li>Page Table: A data structure maintained by the OS to map each virtual page to its corresponding physical frame or secondary storage location.</li><li>Demand Paging: Pages are loaded into physical RAM only when the program actually needs them, rather than loading the entire application at launch.</li><li>Page Fault: An interrupt raised by hardware when a program accesses a page that is not currently in physical RAM, triggering the OS to fetch it from disk.</li><li>Swapping / Paging Out: When RAM is full, the OS moves inactive pages to a designated swap space on secondary storage to free up memory for active tasks.</li></ul>Significance<ul><li>Removes Hardware Limits: Applications can run seamlessly even if their memory footprint exceeds installed physical RAM.</li><li>Process Isolation & Protection: Every process operates in its own isolated virtual address space, preventing buggy or malicious software from reading or overwriting another process's memory.</li><li>Higher Multiprogramming: By only keeping active parts of multiple programs in RAM, the CPU can juggle significantly more tasks simultaneously.</li></ul>Advantages<ul><li>Cost-Efficient Capacity: Expands usable working memory using inexpensive disk storage without requiring physical RAM upgrades.</li><li>Memory Protection: Enhances system stability and security through strict per-process memory boundaries.</li><li>Simplified Programming: Developers do not need to manually manage memory overlays or worry about physical RAM constraints when writing software.</li><li>Efficient Memory Sharing: Common libraries (e.g., standard C runtime or shared DLLs) can be mapped once into physical RAM and shared across multiple processes.</li></ul>Disadvantages<ul><li>Performance Overhead: Address translation adds CPU cycles, though hardware caches like the Translation Lookaside Buffer (TLB) help minimize the latency.</li><li>Risk of Thrashing: If physical RAM is critically low, the system spends more time swapping pages back and forth to the drive than executing instructions, causing extreme lag.</li><li>Disk Wear and Space Consumption: Frequent swapping consumes storage drive space and can increase write cycles on solid-state drives (SSDs).</li><li>Implementation Complexity: Requires complex operating system algorithms for page replacement (such as LRU or FIFO) and specialized hardware support.</li></ul></h2>