Thread (11 messages) 11 messages, 5 authors, 2007-07-29

Re: How can we make page replacement smarter (was: swap-prefetch)

From: Rik van Riel <hidden>
Date: 2007-07-29 04:08:23
Also in: lkml

Al Boldi wrote:
Chris Snook wrote:
quoted
At best, reads can be read-ahead and cached, which is why
sequential swap-in sucks less.  On-demand reads are as expensive as I/O
can get.
Which means that it should be at least as fast as swap-out, even faster 
because write to disk is usually slower than read on modern disks.  But 
linux currently shows a distinct 2x slowdown for sequential swap-in wrt 
swap-out. 
That's because writes are faster than reads in moderate
quantities.

The disk caches writes, allowing the OS to write a whole
bunch of data into the disk cache and the disk can optimize
the IO a bit internally.

The same optimization is not possible for reads.

-- 
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is.  Each group
calls the other unpatriotic.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help