Page that info back into your memory! Virtual Memory Page that info back into your memory!

Simplifying Memory for Applications Applications should see the straightforward memory layout we are familiar with Applications should think they own all of memory Solution: We give them a virtual view of memory

Protection between Processes With a bare system, processes can assigned real physical addresses Which means that nay program can access any address (even one they don’t own) Soln: We should send all addresses through mechanism that OS controls

Mapping Virtual Memory (VM) to Physical Memory (PM) We divide into memory into equal sized chunks (about 4 KiB - 8 KiB)

Mapping Virtual Memory (VM) to Physical Memory (PM) We divide into memory into equal sized chunks (about 4 KiB - 8 KiB), AKA pages!

Mapping VM to PM Any chunk of VM can be mapped to any chunk of PM (“page”)

One Small Problem... We don’t know how large main memory is How does system know which page in VM maps to which one in PM? Use lookup table (page table) to deal with this

Paged Memory Systems Processor-generated address can be split into: A page table contains the physical page number Points to the base of each physical page Makes it possible to store pages of program non-contiguously

Address Mapping in Page Tables Page Table functionality: Incoming request is Virtual Address and we want Physical ADdress Physical Offset = Virtual Offset (since page aligned) We just need to swap the Virtual Page Number (VPN) for Physical Page Number (PPN)

Address Mapping in Page Tables Page Table Implementation Use VPN as index into PT Store PPN and management bits (Valid, Access Rights) Do NOT store data Data sits in PM

Page Table Layout

Page Table Layout

Page Table Layout

Page Table Layout

Page Table Layout

Page Table Layout

What goes inside the Page Table? Contains either PPN or an indication that it doesn’t exist in main memory Valid bit: 1 → virtual page is in physical memory 0 → OS needs to fetch page from disk Access Rights: provides protection Read, write, Executable

One Other Problem... Steps to Retrieve Data 1. Access page table for access translation (lives in PM) 2. Access correct physical address Requires two accesses of physical memory!!!! Solution: build separate cache for Page Table Called Translation Lookaside Buffer (TLB) Stores VPN → PPN Mapping translations

Cache versus TLB

Some more Info on TLB Usually small, typically 32-128 entries Access time comparable to that of cache Usually fully associative (or have high associativity)

Address Translation Using TLB

So how do we get the actual value, now that we have the address? Up to now, usually we would just go to physical memory (or if we’re lucky, just go to the cache). But now, our memory values are distributed between physical memory and disk! Remember the valid bit in the page table entries: Valid bit: 1 → virtual page is in physical memory 0 → OS needs to fetch page from disk Going to physical memory is faster than going to disk, but more expensive ($$$) than disk Solution: put currently used memory values in physical memory (smaller amount), and the rest on Disk (everything else) Sound familiar? It’s caching! Physical memory is a cache for disk! If we have to go to disk, then that’s a page fault (like a cache miss). Only having to go to physical memory is like a cache hit, but doesn’t have a cool name.

Remember caches? Physical memory is a cache for disk! Phys. Memory address Cache (shortcut for phys. memory) Cache Miss Block not in cache, have to go to memory Check the cache In the same way caches dealt in units of blocks (of N bytes), phys. memory has pages (of M > N bytes) Phys. Memory (shortcut for disk) Phys. Memory address Disk Page Fault Check phys. mem. Page not in memory, have to go to disk

Putting it all together (TLB + Cache + MEM + Disk) Address Translation: TLB Miss Phys. Memory address TLB (shortcut for page table) Page Table Virtual Memory address Addr. not in TLB, have to go to page table to translate (translates all virtual addr. in use to pages in phys. addr / disk addr.) Check the TLB TLB Hit Addr. in TLB, can immediately get phys. Addr. translation Accessing contents/value at address: Phys. Memory (shortcut for disk) Cache (shortcut for phys. memory) Phys. Memory address Disk Cache Miss Value/ Contents Page Fault Block not in cache, have to go to memory Check the cache Page not in memory, have to go to disk Wow steven these are so cool ! ! ! Cache Hit Page in phys. memory