> Not for very large files: the forget-behind is absolutely critical in
> that case.
I dunno why you're thinking of unmapping pages though... isn't an mmap
cache the best way to amortize the extra cost of mmap()ing? In that case
you don't want the forget-behind pages to be unmapped. But you do want
them to be dropped from memory when appropriate.
Another thought re: sendfile. The network layer could hint to sendfile as
to the speed of the socket it's delivering to. With that hint and some
suitable queueing theory someone should be able to get a nifty little
algorithm that will "synchronize" sockets as much as possible without
noticeable delays to the user. By "synchronize" I mean getting them going
from the same, or nearby pages. That way on larger than memory data sets
the kernel can sacrifice some latency on a few connections in order to
improve the total throughput.
I won't pretend to have a good heuristic for it ;)
applications: multimedia servers -- audio/video streaming. These boxes
can be limited by disk bandwidth because their data sets are typically
much larger than RAM.
Dean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu