[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!tag open_issue_gnumach open_issue_hurd]] IRC, #hurd, freenode, 2011-02-13: youpi: Would libdiskfs/diskfs.h be in the right place to make readahead functions? etenil: no, it'd rather be at the memory management layer, i.e. mach, unfortunately because that's where you see the page faults youpi: Linux also provides a readahead() function for higher level applications. I'll probably have to add the same thing in a place that's higher level than mach well, that should just be hooked to the same common implementation the man page for readahead() also states that portable applications should avoid it, but it could be benefic to have it for portability it's not in posix indeed IRC, #hurd, freenode, 2011-02-14: youpi: I've investigated prefetching (readahead) techniques. One called DiskSeen seems really efficient. I can't tell yet if it's patented etc. but I'll keep you informed don't bother with complicated techniques, even the most simple ones will be plenty :) it's not complicated really the matter is more about how to plug it into mach ok then don't bother with potential pattents etenil: please take a look at the work KAM did for last year's GSoC just use a trivial technique :) ok, i'll just go the easy way then antrik: what was etenil referring to when talking about prefetching ? oh, madvise() stuff i could help him with that