22.1.8. Translation Lookaside Buffer (TLB)

Virtual memory may be described as the level of memory hierarchy that manages caching between the main memory and disk.

Virtual memory is a memory management capability that allows programs to use more memory than is physically available. It essentially acts as a bridge between the main memory (RAM) and the disk storage. When your computer uses virtual memory, it works by creating an illusion of a large memory space by temporarily transferring data that isn't actively in use from RAM to disk space (known as the swap space or page file). This enables larger applications to run on computers that might not have enough RAM to support them, improving the multitasking capabilities of the operating system.

Think of virtual memory like a library system where the library only has a limited number of shelves (the physical memory), but can still provide access to a huge number of books (the programs) by placing some books in off-site storage (the disk). When a book is needed, the librarian (the operating system) fetches it from the storage and places it on the shelf for access.

It provides address translation from virtual address, used by a program to the physical address space used to access memory.

Address translation is a crucial function in a virtual memory system. Each program operates using virtual addresses, which are then mapped to physical addresses in the RAM. This allows multiple programs to run simultaneously without interfering with each other's memory space. The mapping is typically managed through a data structure called a page table, which keeps track of where each virtual address maps to in the physical memory.

Imagine each virtual address as a house number in a city where the actual houses are scattered across different blocks (physical addresses). The page table acts like a city directory that tells you where to find each house based on its number, helping postal services (the CPU) deliver letters (data) to the correct locations.

It prevents user programs from tampering with page tables so that only the OS can change virtual to physical address translations.

To maintain the integrity of memory, operating systems enforce a protection mechanism that ensures that only authorized code, typically the OS itself, can modify the page tables. This prevents malicious or erroneous user applications from altering the memory mapping, which helps protect the data integrity of other applications running on the system.

Think of it like a secure bank vault where only the bank manager (the OS) has the key to access and modify its contents (the page tables). Regular users (application programs) are allowed to access their accounts (use their memory space) but cannot open the vault to change its security settings.

Controlled sharing is implemented with the help of OS and access bits in the page table that indicate whether a program has read or write access to a page.

Controlled sharing allows multiple running processes to access the same memory locations safely, without causing data corruption. The access bits in the page table control how each page of memory can be accessed. For example, a page might be marked as read-only for one process but writable for another.

Think of accessing library books where some are available for borrowing (write access) while others are only for in-library reading (read-only access). The library's catalog system (the OS) ensures that users do not mistakenly take books that are not for lending.

The cost of page faults is very high. If you have a miss in the main memory you have to go to physical memory.

Page faults occur when a program tries to access a page that is not currently loaded into main memory. When this happens, the operating system must fetch the required page from disk storage, which is significantly slower than accessing data directly from RAM. As a result, excessive page faults can lead to poor system performance, known as thrashing.

This is like going to a grocery store to buy something you forgot on your shopping list. If you keep forgetting and have to make multiple trips, you waste time and energy. Similarly, if a program continually accesses pages not in memory, it slows down overall system performance.

The TLB acts as a cache for address translation from the page table.

The Translation Lookaside Buffer (TLB) is a special cache that stores recent translations of virtual memory addresses to physical memory addresses. This helps speed up the address translation process and reduces the need to access the slower page table in main memory for every memory access, thus improving overall system performance.

Imagine the TLB like a frequently accessed index in a large textbook. Instead of flipping through the entire book (the main memory or page table) to find the information you need, you can quickly check the index (the TLB) to find the page number where that information is located.

--