linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rick.jones2@hp.com (Rick Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] "tcp: refine TSO autosizing" causes performance regression on Xen
Date: Wed, 15 Apr 2015 11:19:15 -0700	[thread overview]
Message-ID: <552EABA3.30109@hp.com> (raw)
In-Reply-To: <1429121303.7346.126.camel@edumazet-glaptop2.roam.corp.google.com>

On 04/15/2015 11:08 AM, Eric Dumazet wrote:
> On Wed, 2015-04-15 at 10:55 -0700, Rick Jones wrote:
>>>
>>> Have you tested this patch on a NIC without GSO/TSO ?
>>>
>>> This would allow more than 500 packets for a single flow.
>>>
>>> Hello bufferbloat.
>>
>> Woudln't the fq_codel qdisc on that interface address that problem?
>
> Last time I checked, default qdisc was pfifo_fast.

Bummer.

> These guys do not want to change a sysctl, how pfifo_fast will magically
> becomes fq_codel ?

Well, I'm not sure that it is George and Jonathan themselves who don't 
want to change a sysctl, but the customers who would have to tweak that 
in their VMs?

rick

  reply	other threads:[~2015-04-15 18:19 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 [this message]
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
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=552EABA3.30109@hp.com \
    --to=rick.jones2@hp.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).