summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDrew DeVault <sir@cmpwn.com>2019-07-19 15:41:10 -0400
committerDrew DeVault <sir@cmpwn.com>2019-07-19 15:41:10 -0400
commita8795f2732b360b5932d54302e8bb8dc919055c4 (patch)
tree474785227765b92bea5eb2763ca7d10827198f2f
parentc3bf8b6bb2505ce10032c46009f1cf6f71583e6c (diff)
Fix exbibytes estimate
-rw-r--r--_posts/2018-10-29-How-does-virtual-memory-work.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2018-10-29-How-does-virtual-memory-work.md b/_posts/2018-10-29-How-does-virtual-memory-work.md
index dc87657..dfb6b93 100644
--- a/_posts/2018-10-29-How-does-virtual-memory-work.md
+++ b/_posts/2018-10-29-How-does-virtual-memory-work.md
@@ -14,7 +14,7 @@ bytes, and in this article I'll explain how.
An astute reader of my earlier article may have considered that pointers on,
say, an x86_64 system, are 64 bits long[^1]. With this, we can address up to
-18,446,744,073,709,551,616 bytes (18.4 exbibytes[^2]) of memory. I only have 16
+18,446,744,073,709,551,616 bytes (16 exbibytes[^2]) of memory. I only have 16
GiB of RAM on this computer, so what gives? What's the rest of the address space
for? The answer: all kinds of things! Only a small subset of your address space
is mapped to physical RAM. A system on your computer called the MMU, or Memory