From: george.dunlap@eu.citrix.com (George Dunlap)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] "tcp: refine TSO autosizing" causes performance regression on Xen
Date: Wed, 15 Apr 2015 19:04:52 +0100 [thread overview]
Message-ID: <552EA844.5010308@eu.citrix.com> (raw)
In-Reply-To: <1429120373.7346.125.camel@edumazet-glaptop2.roam.corp.google.com>
On 04/15/2015 06:52 PM, Eric Dumazet wrote:
> On Wed, 2015-04-15 at 18:41 +0100, George Dunlap wrote:
>
>> So you'd be OK with a patch like this? (With perhaps a better changelog?)
>>
>> -George
>>
>> ---
>> TSQ: Raise default static TSQ limit
>>
>> A new dynamic TSQ limit was introduced in c/s 605ad7f18 based on the
>> size of actual packets and the amount of data being transmitted.
>> Raise the default static limit to allow that new limit to actually
>> come into effect.
>>
>> This fixes a regression where NICs with large transmit completion
>> times (such as xennet) had a 30% hit unless the user manually tweaked
>> the value in /proc.
>>
>> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
>>
>> diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
>> index 1db253e..8ad7cdf 100644
>> --- a/net/ipv4/tcp_output.c
>> +++ b/net/ipv4/tcp_output.c
>> @@ -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;
>> +/* Static TSQ limit. A more dynamic limit is calculated in
>> tcp_write_xmit. */
>> +int sysctl_tcp_limit_output_bytes __read_mostly = 1048576;
>>
>> /* This limits the percentage of the congestion window which we
>> * will allow a single TSO frame to consume. Building TSO frames
>>
>
> Have you tested this patch on a NIC without GSO/TSO ?
>
> This would allow more than 500 packets for a single flow.
>
> Hello bufferbloat.
>
> So my answer to this patch is a no.
You said:
"I asked you guys to make a test by increasing
sysctl_tcp_limit_output_bytes You have no need to explain me the code I
wrote, thank you."
Which implies to me that you think you've already pointed us to the
answer you want and we're just not getting it.
Maybe you should stop wasting all of our time and just tell us what
you're thinking.
-George
next prev parent reply other threads:[~2015-04-15 18:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 15:46 "tcp: refine TSO autosizing" causes performance regression on Xen Stefano Stabellini
2015-04-09 16:16 ` Eric Dumazet
2015-04-09 16:36 ` Stefano Stabellini
2015-04-09 17:07 ` Eric Dumazet
2015-04-13 10:56 ` [Xen-devel] " George Dunlap
2015-04-13 13:38 ` Jonathan Davies
2015-04-13 13:49 ` Eric Dumazet
2015-04-15 13:43 ` George Dunlap
2015-04-15 16:38 ` Eric Dumazet
2015-04-15 17:23 ` George Dunlap
2015-04-15 17:29 ` Eric Dumazet
2015-04-15 17:41 ` George Dunlap
2015-04-15 17:52 ` Eric Dumazet
2015-04-15 17:55 ` Rick Jones
2015-04-15 18:08 ` Eric Dumazet
2015-04-15 18:19 ` Rick Jones
2015-04-15 18:32 ` Eric Dumazet
2015-04-15 20:08 ` Rick Jones
2015-04-15 18:04 ` George Dunlap [this message]
2015-04-15 18:19 ` Eric Dumazet
2015-04-16 8:56 ` George Dunlap
2015-04-16 9:20 ` Daniel Borkmann
2015-04-16 10:01 ` George Dunlap
2015-04-16 12:42 ` Eric Dumazet
2015-04-20 11:03 ` George Dunlap
2015-06-02 9:52 ` Wei Liu
2015-06-02 16:16 ` Eric Dumazet
2015-04-16 9:22 ` David Laight
2015-04-16 10:57 ` George Dunlap
2015-04-15 17:41 ` Eric Dumazet
2015-04-15 17:58 ` Stefano Stabellini
2015-04-15 18:17 ` Eric Dumazet
2015-04-16 4:20 ` Herbert Xu
2015-04-16 4:30 ` Eric Dumazet
2015-04-16 11:39 ` George Dunlap
2015-04-16 12:16 ` Eric Dumazet
2015-04-16 13:00 ` Tim Deegan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552EA844.5010308@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).