All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: ncardwell@google.com, eric.dumazet@gmail.com,
	dave.taht@bufferbloat.net, netdev@vger.kernel.org
Subject: Re: 16% regression on 10G caused by TCP small queues
Date: Wed, 23 Oct 2013 21:45:57 -0700	[thread overview]
Message-ID: <20131023214557.386aad1a@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20131023.233816.1396918839771657154.davem@davemloft.net>

On Wed, 23 Oct 2013 23:38:16 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:

> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Wed, 23 Oct 2013 20:09:49 -0700
> 
> > I will check 3.12, but what about users on 3.10 which is the LTS
> > kernel used by most distros?

3.12-rc6 gets line rate again (9.41 Gbit/sec)

> The fix will be backported to -stable, relax Stephen.

Sorry, thought sk_pacing_rate depended on FQ qdisc but it is other way around.
In which case doing merge of these two was sufficient to fix the problem.
With a minor manual fix up to tcp.h.


commit 95bd09eb27507691520d39ee1044d6ad831c1168
Author: Eric Dumazet <edumazet@google.com>
Date:   Tue Aug 27 05:46:32 2013 -0700

    tcp: TSO packets automatic sizing

commit c9eeec26e32e087359160406f96e0949b3cc6f10
Author: Eric Dumazet <edumazet@google.com>
Date:   Fri Sep 27 03:28:54 2013 -0700

    tcp: TSQ can use a dynamic limit

  reply	other threads:[~2013-10-24  4:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  2:29 16% regression on 10G caused by TCP small queues Stephen Hemminger
2013-10-24  2:37 ` Neal Cardwell
2013-10-24  3:09   ` Stephen Hemminger
2013-10-24  3:38     ` David Miller
2013-10-24  4:45       ` Stephen Hemminger [this message]
2013-10-24  6:05         ` Eric Dumazet
2013-10-24  6:10         ` Eric Dumazet
2013-10-24  6:19           ` Eric Dumazet
2013-10-24  7:01         ` David Miller
2013-10-27  4:33           ` Dave Taht
2013-10-27  5:07             ` David Miller

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=20131023214557.386aad1a@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=dave.taht@bufferbloat.net \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.