This is exactly why we want to do proper read-behind...
There are quite a lot of programs that do tiled backwards
reading of data, just think about large matrix stuff or
some image viewing or manipulation stuff.
It is relatively cheap to do read-behind, so I don't see
any reason to let the backwards-reading programs slow
down the rest of the system by causing 'improper' disk
access patterns.
We can simply implement the read-behind in the same way
we do read-ahead, but we start at address-16 instead of
address itself.
cheers,
Rik -- the flu hits, the flu hits, the flu hits -- MORE
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/