AFIK the bench was not with 2.4.10 (not that I remeber any missing fsync
anyways, actually MS_ASYNC is broken and this is fixed between in
18pre2aa2 from Andrew Morton, but that was broken in 2.4.[79] too). The
bench in 2.2 was delivering much better performance than with 2.4 (I
don't recall the exact number) and 2.2 definitely is not missing fsync
etc... furthmore the 2.2 numbers were reproducible. the benchmark swaps
heavily shm etc... and the 2.4.[79] vm was collapsing at the second pass
(I think first throughput was 5 then 1 1 1 1), if you swapout always the
wrong part and you start trashing because of unbalance of aging it is
very easy to make a x10 difference in the final numbers. I think a sane
vm should run faster than 2.2 and to be reproducible as 2.2. I tend to
like such test, also because it is a real life test (unlike what
somebody thought). The huge regression in such test was one of the main
reasons that made me to realize the brokeness of the vm algorithms.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/