9.1. Basics of Virtual Memory and Address Translation

In this module we will start our discussion with Virtual Memory. In the previous modules we had studied caches which provide fast access to a processes code and data. In a similar way we will now study a technique which allows the main memory to be used as a cache for the secondary storage. And this mechanism is jointly managed by both the OS, and the CPU hardware.

Virtual memory is a memory management technique that creates an illusion of a large memory space to applications running on a computer, by use of both primary (RAM) and secondary storage (like a hard disk). This method helps optimize the performance of applications by allowing more processes to run concurrently in main memory. It achieves this by allowing active portions of multiple processes to be resident in main memory at the same time, facilitating efficient CPU usage.

Think of virtual memory like an efficient filing system in a library. Instead of having every book on the shelf (which can be limited space), the library keeps some books in a storage facility (secondary storage) and only brings them to the shelf (main memory) when someone requests them. This allows the library to effectively manage space and provide access to many more titles than it physically has room for.

Before execution each process gets a range of virtual memory locations to address its data and code. So, as we are talking this is virtual memory it does not exist in practice. So, when we are combining when the program is being compiled it assumes that it has a range of memory locations at its disposal.

Virtual addresses are the memory locations assigned to each process by the operating system. These addresses do not correspond to actual physical locations in RAM. Instead, they act as an abstraction, allowing programs to 'think' they have a large address space available. This makes programming easier since developers can write code without worrying about the physical memory layouts.

Imagine using a map of a city where each location is labeled with an address. When you look for a restaurant, you use the map (virtual address) rather than needing to know the exact GPS coordinates (physical address). The map enables you to navigate efficiently without understanding the underlying complexities of the city's layout.

So, the virtual addresses that are generated by the CPU must be mapped to physical addresses. So, I generate a virtual address there will be a mapping process, the memory management unit will map this virtual address into a physical address; that means, where this data that I have accessed will actually reside in main memory.

When a program runs and generates a virtual address, that address must be translated into a physical address where the data actually resides in RAM. This translation is handled by a component called the Memory Management Unit (MMU). The MMU ensures that each virtual address is correctly mapped to the corresponding physical address, allowing the CPU to fetch the correct data efficiently.

Think of this mapping as a postal system. When you send a letter (virtual address), you write a clear address on the envelope. The postal service (MMU) takes your letter and makes sure it reaches the exact location (physical address) so the recipient (CPU) can read it. If the address is incorrect, the letter won't arrive at the right destination.

Now this translation from virtual addresses of a process to the physical address is done together by the CPU, and OS. And what do you get additionally that this translation process also enforces protection of a programs physical address space from other programs.

The translation process not only maps virtual addresses to physical addresses but also protects the memory space of each program from interference by others. This is crucial in a multi-tasking environment where multiple programs run simultaneously. By ensuring that each program can only access its designated memory addresses, the operating system maintains stability and security.

Consider a shared apartment building where each tenant (program) has their own locked room (memory space). Even though the building is shared, each tenant cannot enter another tenant's room without permission (protection). This separation allows everyone to feel secure, knowing that their belongings (data) are safe.

Now how do we do this mapping from virtual to physical addresses? So, both the virtual and physical memory; so the virtual memory and the physical memory are broken into blocks of the same size... Now, the virtual memory translation miss is called a page fault; that means, during translation I have my CPU asked for data corresponding to a virtual address.

When the CPU requests data using a virtual address, it may find that the corresponding physical address isn't currently loaded in memory. This is known as a page fault. The system then must load the required data from secondary storage into RAM. The handling of page faults is a critical part of virtual memory management, ensuring that programs can access the data they need, even if it's not immediately in RAM.

Imagine trying to access a book in a library (your active undercurrent) that isn't on the shelf (in RAM). The librarian (operating system) must retrieve this book from the storage room (secondary storage). While this process takes some time, it allows you to access books that are occasionally stored away, improving the library's overall efficiency.

So, the same physical memory page can be mapped can be pointed to by multiple virtual addresses for example, in this case here this virtual page and this virtual page points to the same physical page frame this one.

Pages in virtual memory can be shared among multiple programs. This means that the same physical page of memory can be mapped to different virtual pages from different processes. This is particularly useful for things like shared libraries, where many programs may need to use the same code.

Think of a shared resource such as a community pool. Multiple families (programs) can use it simultaneously without needing their own separate pools (physical memory). Instead of each family building their own pool, they enjoy the benefits of one shared facility, fostering cooperation and resource optimization.

So, virtual to physical address translation a logical address generated by the CPU is broken into a virtual page number and a page offset.

In summary, virtual memory management is central to modern operating systems. By keeping processes isolated, mapping virtual addresses to physical memory, and handling page faults efficiently, operating systems ensure that applications run smoothly while utilizing hardware resources effectively.

Think of using a personal organizer where you can write down tasks (virtual addresses) that you'll attend to later. The organization has a system for prioritizing and scheduling tasks even if you can't do them all at once. This system ensures that you stay productive without needing to get overwhelmed, similar to how virtual memory allows systems to run efficiently even with limited physical memory.

--