> Hmmm, arguably reading pages we do not want is a mistake. I should think that
> if a big performance win is required to justify a design choice, it should
> be especially required to show such a win for doing something that on its
> face is wrong.
The case for files and has already been justified.
The performance gain of reading pages that are contiguous on disk has
been justified.
The only problem thing that has not been shown is that swap pages that
are used together are located near each other in swap.
As for design choices simplicity, maintainability and
comprehensiblility, tend to be more important than absolute
performance. This lets bugs be fixed, and the big changes that tend
to be the biggest wins happen.
> I am skeptical of the argument that we can win by replacing "the least
> desirable" pages with pages were even less desireable and that we have
> no recent indication of any need for. It seems possible under heavy swap
> to discard quite a portion of the useful pages in favor of junk that just
> happenned to have a lucky disk address.
I won't argue that. My gut just says we should work to improve the
disk addresses, so it isn't luck. ;) And only if we fail in that
hack up the efficient simple policy, that we have for reading disk
data in.
Of course since I'm not actually writing the code at the moment
this is all hot air :)
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/