summaryrefslogtreecommitdiff
path: root/open_issues/performance/io_system/read-ahead.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2011-02-17 14:15:11 +0100
committerThomas Schwinge <thomas@schwinge.name>2011-02-17 14:15:11 +0100
commitbdd896e0b81cfb40c8d24a78f9022f6cd1ae5e8c (patch)
treeb910b9f770f08a7f0bc5951025db358f03dfffd7 /open_issues/performance/io_system/read-ahead.mdwn
parent5aef0778f741625959e4d474cac3e6c783c78175 (diff)
open_issues/performance/io_system/clustered_page_faults: New. And some more IRC discussions.
Diffstat (limited to 'open_issues/performance/io_system/read-ahead.mdwn')
-rw-r--r--open_issues/performance/io_system/read-ahead.mdwn19
1 files changed, 19 insertions, 0 deletions
diff --git a/open_issues/performance/io_system/read-ahead.mdwn b/open_issues/performance/io_system/read-ahead.mdwn
index 241cda41..3ee30b5d 100644
--- a/open_issues/performance/io_system/read-ahead.mdwn
+++ b/open_issues/performance/io_system/read-ahead.mdwn
@@ -278,3 +278,22 @@ IRC, freenode, #hurd, 2011-02-15
<antrik> BTW, I remembered now that KAM's GSoC application should have a
pretty good description of the necessary changes... unfortunately, these
are not publicly visible IIRC :-(
+
+---
+
+IRC, freenode, #hurd, 2011-02-16
+
+ <etenil> braunr: I've looked in the kernel to see where prefetching would
+ fit best. We talked of the VM yesterday, but I'm not sure about it. It
+ seems to me that the device part of the kernel makes more sense since
+ it's logically what manages devices, am I wrong?
+ <braunr> etenil: you are
+ <braunr> etenil: well
+ <braunr> etenil: drivers should already support clustered sector
+ read/writes
+ <etenil> ah
+ <braunr> but yes, there must be support in the drivers too
+ <braunr> what would really benefit the Hurd mostly concerns page faults, so
+ the right place is the VM subsystem
+
+[[clustered_page_faults]]