BTW. while your patchset might be nicely broken down, I think your
naming and descriptions are letting it down a little bit.
Wu Fengguang wrote:
Aggressive readahead policy for read on start-of-file.
Instead of selecting a conservative readahead size,
it tries to do large readahead in the first place.
However we have to watch on two cases:
- do not ruin the hit rate for file-head-checkers
- do not lead to thrashing for memory tight systems
How does it handle
- don't needlessly readahead too much if the file is in cache
Would the current readahead mechanism benefit from more aggressive
start-of-file
readahead?
--
Send instant messages to your online friends http://au.messenger.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
