tcp: double default TSQ output bytes limit
Xen virtual network driver has higher latency than a physical NIC. Having only 128K as limit for TSQ introduced 30% regression in guest throughput. This patch raises the limit to 256K. This reduces the regression to 8%. This buys us more time to work out a proper solution in the long run. Signed-off-by: Wei Liu <wei.liu2@citrix.com> Cc: David Miller <davem@davemloft.net> Cc: Eric Dumazet <eric.dumazet@gmail.com> Acked-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
12e25e1041
commit
c39c4c6abb
|
@ -50,8 +50,8 @@ int sysctl_tcp_retrans_collapse __read_mostly = 1;
|
|||
*/
|
||||
int sysctl_tcp_workaround_signed_windows __read_mostly = 0;
|
||||
|
||||
/* Default TSQ limit of two TSO segments */
|
||||
int sysctl_tcp_limit_output_bytes __read_mostly = 131072;
|
||||
/* Default TSQ limit of four TSO segments */
|
||||
int sysctl_tcp_limit_output_bytes __read_mostly = 262144;
|
||||
|
||||
/* This limits the percentage of the congestion window which we
|
||||
* will allow a single TSO frame to consume. Building TSO frames
|
||||
|
|
Loading…
Reference in New Issue