The 2.4 VM's virtual scan has the effect of swapping out one process at a
time. 2.5's physical(ish) scan doesn't have that side-effect.
It means that in 2.4, the lucky processes can make decent progress. In
2.5, everyone makes equal progress and everyone thrashes everyone else to
To fix this properly we need load control: to identify when the system is
thrashing and to explicitly suspend chosen processes for a while, so other
processes can make decent progress. A couple of people are looking at
that; I'm not sure what stage it is at.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/