linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 16 Apr 2015 09:56:22 +0100	[thread overview]
Message-ID: <552F7936.9070205@eu.citrix.com> (raw)
In-Reply-To: <1429121979.7346.138.camel@edumazet-glaptop2.roam.corp.google.com>

On 04/15/2015 07:19 PM, Eric Dumazet wrote:
> On Wed, 2015-04-15 at 19:04 +0100, George Dunlap wrote:
> 
>> Maybe you should stop wasting all of our time and just tell us what
>> you're thinking.
> 
> I think you make me wasting my time.
> 
> I already gave all the hints in prior discussions.

Right, and I suggested these two options:

"Obviously one solution would be to allow the drivers themselves to set
the tcp_limit_output_bytes, but that seems like a maintenance
nightmare.

"Another simple solution would be to allow drivers to indicate whether
they have a high transmit latency, and have the kernel use a higher
value by default when that's the case." [1]

Neither of which you commented on.  Instead you pointed me to a comment
that only partially described what the limitations were. (I.e., it
described the "two packets or 1ms", but not how they related, nor how
they related to the "max of 2 64k packets outstanding" of the default
tcp_limit_output_bytes setting.)

 -George


[1]
http://marc.info/?i=<CAFLBxZYt7-v29ysm=f+5QMOw64_QhESjzj98udba+1cS-PfObA@mail.gmail.com>

  reply	other threads:[~2015-04-16  8:56 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
2015-04-15 18:19                       ` Eric Dumazet
2015-04-16  8:56                         ` George Dunlap [this message]
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=552F7936.9070205@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).