Back
All Modules Memory Management Virtual Memory & Paging

Virtual Memory & Paging

How each process gets a clean address space from messy physical RAM: pages, page tables, TLBs, faults, and replacement.

0 / 22 solved
0/22 solved
Question Tags Difficulty Success
1. Page set
Memory ManagementOperating Systems
Medium 54%
2. Private Writes Vanish
mmapcopy-on-write +2
 Medium 76%
3. Virtual Page Number vs Physical Frame Number
vpnpfn +4
 Medium 86%
4. Private Means Private
mmapcopy-on-write +2
 Medium 88%
5. Nine Bytes Of Fork
copy-on-writefork +2
 Medium 44%
6. One Byte Every Four Kilobytes
demand-paginganonymous-memory +2
 Medium 64%
7. Why Not Sixty-Four Kilobytes
page-sizeinternal-fragmentation +2
 Medium 67%
8. More Frames More Pain
page-replacementfifo +2
 Medium 67%
9. Two Writes Out Of Four
dirty-bitpage-replacement +2
 Medium 90%
10. Forty Nine Of Fifty
page-replacementlru +2
 Medium 67%
11. Twelve Kilobytes Of Tables
pagingmulti-level-page-table +2
 Medium 58%
12. Page Fault Types
Operating SystemsMemory Management
Medium 53%
13. Four Megabytes Of Nothing
page-tablepte +2
 Medium 71%
14. Valid But Not Present
demand-pagingpage-fault +2
 Medium 96%
15. The Hand Sweeps Once
clock-algorithmpage-replacement +2
 Medium 60%
16. Four Percent Busy
thrashingworking-set +2
 Medium 83%
17. Two Levels To One Byte
address-translationpage-directory +2
 Medium 50%
18. Three Different Faults
page-faultpresent-bit +2
 Hard 73%
19. Memory-Mapped Files 1
Memory ManagementOperating Systems
Hard 74%
20. Dirty Page Writeback
Memory ManagementOperating Systems
Hard 64%
21. Seven Pages Of Tables
pagingmulti-level-page-tables +2
 Hard 57%
22. Who Clears The Dirty Bit
page-table-entrydirty-bit +2
 Hard —

Learning Resources

Operating Systems: Three Easy Pieces, Chapters 15, 16, 18, 20, 21, 22, 23

Up next

22 of 22 questions here are still unsolved.

Next module Allocators