netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@fedoraproject.org>
To: Yuchung Cheng <ycheng@google.com>
Cc: Michael Sterrett <michael@sterretts.net>,
	netdev <netdev@vger.kernel.org>,
	Neal Cardwell <ncardwell@google.com>,
	Nandita Dukkipati <nanditad@google.com>
Subject: Re: 3.10.0 network trace
Date: Wed, 11 Sep 2013 21:51:58 -0400	[thread overview]
Message-ID: <CA+5PVA4YmFVy=02Py2+1=BP4MbcCrUKphk7w+0-ahvMPxygt_g@mail.gmail.com> (raw)
In-Reply-To: <CAK6E8=eRZQnPeVPpzcdzUtLqr0n2kjUQ2_JRE8_WXn3sSV2y9A@mail.gmail.com>

On Wed, Sep 11, 2013 at 12:32 PM, Yuchung Cheng <ycheng@google.com> wrote:
> On Wed, Sep 11, 2013 at 5:49 AM, Josh Boyer <jwboyer@fedoraproject.org> wrote:
>> On Sun, Jul 21, 2013 at 9:36 PM, Michael Sterrett <michael@sterretts.net> wrote:
>>> Since upgraded to 3.10.1 which exhibits the same issue (probably not
>>> surprising).
>>>
>>> sysctl net.ipv4.tcp_frto=0 net.ipv4.tcp_early_retrans=3 seems to take
>>> care of it.
>>
>> We're still getting reports of this with 3.10.10 in Fedora [1].  At
>> least one of the reporters has said those sysctl settings didn't help.
>>
>> Is there anything else that can be gathered to help track this down?
> since frto=0 didn't help, I suspect it's either a bug introduced in
> the tail loss probe patch 9b717a8d (tcp: TLP loss detection) or other
> changes related loss recovery.
>
> could you try disable TLP by
> sysctl net.ipv4.tcp_frto=0 net.ipv4.tcp_early_retrans=1
>
> if it still does not work. disable any form of early retransmit by
> sysctl net.ipv4.tcp_frto=0 net.ipv4.tcp_early_retrans=0

Thanks.  I've asked the people in the bug to try those settings.

> if you can test a custom build kernel, please try this debugging patch.

I'll get the patch included in a test build for the tomorrow as well.

josh

      reply	other threads:[~2013-09-12  1:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+rTEUPfP8ouJHbaFrO=-zktg2D06kYgXOq-LnmyKbbEzj-TmA@mail.gmail.com>
2013-07-12 20:44 ` Fwd: 3.10.0 network trace Michael Sterrett
2013-07-12 21:18   ` Yuchung Cheng
2013-07-12 21:33     ` Michael Sterrett
2013-07-12 21:39       ` Yuchung Cheng
2013-07-13 21:10         ` Michael Sterrett
2013-07-21  6:04           ` Yuchung Cheng
2013-07-22  1:36             ` Michael Sterrett
2013-09-11 12:49               ` Josh Boyer
2013-09-11 16:32                 ` Yuchung Cheng
2013-09-12  1:51                   ` Josh Boyer [this message]

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='CA+5PVA4YmFVy=02Py2+1=BP4MbcCrUKphk7w+0-ahvMPxygt_g@mail.gmail.com' \
    --to=jwboyer@fedoraproject.org \
    --cc=michael@sterretts.net \
    --cc=nanditad@google.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=ycheng@google.com \
    /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).