diff options
| -rw-r--r-- | user/Etenil.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/user/Etenil.mdwn b/user/Etenil.mdwn index a19aacd8..f19a5697 100644 --- a/user/Etenil.mdwn +++ b/user/Etenil.mdwn @@ -18,14 +18,14 @@ Write a clusterized pagein (prefetching) mechanism in Mach. ## General information on system architecture -In order to implement the pagein properly, it was necessary for me to get a general idea of the I/O path that data follows in the Hurd/Mach. To accomplish this, I've investigated top-down from the [[ext2fs]] translator to Mach. This section contains the main nodes that data passes through. +In order to implement the pagein properly, it was necessary for me to get a general idea of the I/O path that data follows in the Hurd/Mach. To accomplish this, I've investigated top-down from the [[hurd/translator/ext2fs]] translator to Mach. This section contains the main nodes that data passes through. This section is probably unnecessary to implement the prefetcher in Mach, however it is always interesting to understand how things work so we can notice when they get broken. This is based on my understanding of the system and is probably imprecise. Refer to the manuals of both Hurd and Mach for more detailed information. ### Pagers -Pagers are implemented in libpager and provide abstracted access to Mach's [[VM]]. A pager is a struct that contains callback function references. These are used to actually access the storage. In the case of FS translators, like ext2fs, the pager uses libstore to acess the underlying hardware. +Pagers are implemented in libpager and provide abstracted access to Mach's [[microkernel/mach/virtual address space]]. A pager is a struct that contains callback function references. These are used to actually access the storage. In the case of FS translators, like ext2fs, the pager uses libstore to acess the underlying hardware. ### Libstore Libstore provides abstracted access to Mach's storage access. |