On Fri, 2011-10-28 at 13:19 -0700, Dan Magenheimer wrote: > For those who "hack on the VM", I can't imagine why the handful > of lines in the swap subsystem, which is probably the most stable > and barely touched subsystem in Linux or any OS on the planet, > is going to be a burden or much of a cost. Saying things like this doesn't encourage anyone to trust you. The whole of the MM is a complex, highly interacting system. The recent issues we've had with kswapd and the shrinker code gives a nice demonstration of this ... and that was caused by well tested code updates. You can't hand wave away the need for benchmarks and performance tests. You have also answered all questions about inactive cost by saying "the code has zero cost when it's compiled out" This also is a non starter. For the few use cases it has, this code has to be compiled in. I suspect even Oracle isn't going to ship separate frontswap and non-frontswap kernels in its distro. So you have to quantify what the performance impact is when this code is compiled in but not used. Please do so. James -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>