summaryrefslogtreecommitdiff
path: root/user
diff options
context:
space:
mode:
authormcsim <mcsim@web>2012-06-15 16:27:10 +0200
committerGNU Hurd web pages engine <web-hurd@gnu.org>2012-06-15 16:27:10 +0200
commitbdb5476b45b43e1753514fe28d1be9436dd572bd (patch)
tree5ffcbae92cd8f4766e58a6c9bc0cf06f1140ff07 /user
parent70296d584c1730785c511baef6edf18c8d0f4fbc (diff)
Diffstat (limited to 'user')
-rw-r--r--user/Maksym_Planeta.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/user/Maksym_Planeta.mdwn b/user/Maksym_Planeta.mdwn
index 91f3cc6a..fccf3840 100644
--- a/user/Maksym_Planeta.mdwn
+++ b/user/Maksym_Planeta.mdwn
@@ -13,7 +13,7 @@ License|/fdl]]."]]"""]]
15.06.12
-Explored gnumach code. First I was reimplementing vm_fault_page as coroutine that returns before executing of mo_data_{unlock,request} calls to vm_fault. vm_fault had to analyse state of vm_fault_page for every page in loop and make a decision regarding further behavior (call mo_data_*, go to next page, etc.). But than I've got that this way is much worse, than doing everything in vm_fault_page (like in OSF mach), so I made a back-off and started working on clustered paging from the beginning (at least now I see clearer how things should be).
+Explored gnumach code. First I was reimplementing vm_fault_page as coroutine that returns before executing of mo_data_{unlock,request} calls to vm_fault. vm_fault had to analyse state of vm_fault_page for every page in loop and make a decision regarding further behavior (call mo_data_*, go to next page, etc.). But than I've got that this way is much worse, than doing everything in vm_fault_page (like in OSF mach), so I made a back-off and started working on clustered paging from the beginning (at least now I see clearer how things should be). At the moment I review kam's patch one more time and looked through mklinux code attentively.
8.06.12