Re: Major network performance regression in 3.7
From: Eric Dumazet
Date: Sun Jan 06 2013 - 09:58:51 EST
On Sun, 2013-01-06 at 10:24 +0100, Willy Tarreau wrote:
> It does not change anything to the tests above unfortunately. It did not
> even stabilize the unstable runs.
> I'll check if I can spot the original commit which caused the regression
> for MTUs that are not n*4096+52.
Since you don't post your program, I wont be able to help, just by
guessing what it does...
TCP has very low defaults concerning initial window, and it appears you
set RCVBUF to even smaller values.
Here we can see "win 8030", this is not a sane value...
18:32:08.071602 IP 127.0.0.1.26792 > 127.0.0.1.8000: S 2036886615:2036886615(0) win 8030 <mss 65495,nop,nop,sackOK,nop,wscale 9>
18:32:08.071605 IP 127.0.0.1.8000 > 127.0.0.1.26792: S 126397113:126397113(0) ack 2036886616 win 8030 <mss 65495,nop,nop,sackOK,nop,wscale 9>
So you apparently changed /proc/sys/net/ipv4/tcp_rmem or SO_RCVBUF ?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/