summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormcsim <mcsim@web>2011-11-06 21:10:45 +0100
committerGNU Hurd web pages engine <web-hurd@gnu.org>2011-11-06 21:10:45 +0100
commitf8dc61388c5c7ea1bc2bf1984d3c85de76c8c837 (patch)
tree4a247030a139db8069052eddcbb99009f31945e6
parentc4b6c1d7714426b9ceb204b5a26553aafdd5a265 (diff)
-rw-r--r--user/Maksym_Planeta.mdwn23
1 files changed, 21 insertions, 2 deletions
diff --git a/user/Maksym_Planeta.mdwn b/user/Maksym_Planeta.mdwn
index 64dc6e19..3872bc68 100644
--- a/user/Maksym_Planeta.mdwn
+++ b/user/Maksym_Planeta.mdwn
@@ -9,8 +9,27 @@ is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!toc]]
-Notes on tmpfs
-==============
+#Notes on tmpfs
+
+## mach-defpager
+
+ <tschwinge>: 1. On every system there is a ``default pager'' (mach-defpager). That one is responsible
+ for all ``anonymous memory''. For example, when you do malloc(10 MiB), and then there is memory pressure,
+ this 10 MiB memory region is backed by the default pager, whose job then is it to provide the backing store for this.
+ <tschwinge>: This is what commonly would be known as a swap partition.
+ <tschwinge>: And this is also the way tmpfs works (as I understand it).
+ <tschwinge>: malloc(10 MiB) can also be mmap(MAP_ANONYMOUS, 10 MIB); that's the same, essentially.
+ <tschwinge>: Now, for ext2fs or any other disk-based file system, this is different:
+ <tschwinge>: The ext2fs translator implements its own backing store, namely it accesses the disk for storing
+ changed file content, or to read in data from disk if a new file is opened.
+
+## Steps
+
+1. Find out what causes crashes in tmpfs with defpager
+
+2. Write own pager
+
+ 6.11.11 Reading/writing for files that fit in vm_page_size works
#Debugging