Mmm, maybe not.
> Make sure you benchmark FPU intensive use when testing USE_3DNOW. I've
> seen several situations where it looks marginally better until you
> actually measure two things - memory bandwidth available to user
> programs, and also FPU performance, especially of FPU heavy apps that
> schedule a lot (eg Quake)
Thanks for helping me narrow the search. On an allocate and write to
pages of memory test, USE_3DNOW increased test time by 15% (which is
bad) on k6-2.
Both kernels compiled with gcc-3.1.0 -march=k6-2.
mtest01 -w 50 executed 100 times
CONFIG_X86_USE_3DNOW=n 745 seconds
CONFIG_X86_USE_3DNOW=y 860 seconds
-- Randy Hron- 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/