summaryrefslogtreecommitdiff
path: root/user
diff options
context:
space:
mode:
authorhttp://etenil.myopenid.com/ <http://etenil.myopenid.com/@web>2011-02-18 19:50:45 +0000
committerGNU Hurd web pages engine <web-hurd@gnu.org>2011-02-18 19:50:45 +0000
commitd22a3b299d00ce757237f9aee9794d0d4f2758e2 (patch)
tree0c48d9722852b219da2999b630c0c29013432261 /user
parent10f09a840a214787e1d8d39807866849e88aeada (diff)
Diffstat (limited to 'user')
-rw-r--r--user/Etenil.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/user/Etenil.mdwn b/user/Etenil.mdwn
index 603bbdec..a1a3373b 100644
--- a/user/Etenil.mdwn
+++ b/user/Etenil.mdwn
@@ -27,7 +27,7 @@ This is where the problem lies. Hard disks are inherently efficient at sequentia
There are a couple of ways I could think of to solve this problem. Pages could be enlarged, but that would cause a lot more problems. Or pages must be handled by groups instead of one by one. This means the changes will also need to be applied in the way user-space processes talk to Mach.
## What's already been done
-[[hurd/user/KAM]] has already made a patch that provides basic page clustering. I have yet to understand it completely, but there are troubling changes in the patch, most notably the removal of continuations in *vm_fault* and *vm_fault_page*.
+[[user/KAM]] has already made a patch that provides basic page clustering. I have yet to understand it completely, but there are troubling changes in the patch, most notably the removal of continuations in *vm_fault* and *vm_fault_page*.
So far, what I can tell is that KAM seems to have modified the memory objects in Mach so that they handle clusters of pages.