There's no sense denying evidence that 2.2 outperforms 2.4 under certain
workloads. Instead we should just be more determined to root out all
those problems and deal with them. There is no inherent design reason
why 2.4 should be slower than 2.2 in any area at all, however, some
practical issues, such as IO scheduling still remain and are being
actively worked on. Expect backports from 2.5 later in the 2.4 series.
For now, the one thing we must not do is risk instability in 2.4, now
that most users have switched over to it.
-- Daniel - 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/