Ok, this makes things more interesting .... What worked for a XEON doesnt work the same way for an opteron.
For me, the copybreak (in its capacity as adding extra cycles that make the prefetch look good) made things look good. Also, #125 gave a best answer. None of these were the case from Roberts results. Robert, what about just #1? Maybe thats the best compromise that would work for all. Also, I am really hoping that someone will test with older hardware where i claim to have seen prefetch causing problems. cheers, jamal On Mon, 2005-12-12 at 16:36 +0100, Robert Olsson wrote: > jamal writes: > > > Could the Robert/Jesse also verify this? I normally dont get excited by > > an extra kpps these days;-> > > Hello! > > Here is a summary. It compares #12 and #125 prefetches with different load > and with and without copybreak. > > cpybrk load prefetch tput kpps > --------------------------------------- > N 2*single #12 1352 > N 2*32k flows #12 766 > N 2*single #125 1314 > N 2*32k flows #125 772 > > Y 2*single #12 1299 > Y 2*32k flows #12 702 > Y 2*single #125 1296 > Y 2*32k flows #125 686 > > According to this prefetch #1 and #2 seems to be a good start. > > Cheers. > - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
