netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ncardwell@google.com
Cc: netdev@vger.kernel.org, ycheng@google.com, soheil@google.com
Subject: Re: [PATCH net] tcp_bbr: fix pacing_gain to always be unity when using lt_bw
Date: Thu, 01 Feb 2018 09:44:22 -0500 (EST)	[thread overview]
Message-ID: <20180201.094422.1284279400896772062.davem@davemloft.net> (raw)
In-Reply-To: <20180131204305.236274-1-ncardwell@google.com>

From: Neal Cardwell <ncardwell@google.com>
Date: Wed, 31 Jan 2018 15:43:05 -0500

> This commit fixes the pacing_gain to remain at BBR_UNIT (1.0) when
> using lt_bw and returning from the PROBE_RTT state to PROBE_BW.
> 
> Previously, when using lt_bw, upon exiting PROBE_RTT and entering
> PROBE_BW the bbr_reset_probe_bw_mode() code could sometimes randomly
> end up with a cycle_idx of 0 and hence have bbr_advance_cycle_phase()
> set a pacing gain above 1.0. In such cases this would result in a
> pacing rate that is 1.25x higher than intended, potentially resulting
> in a high loss rate for a little while until we stop using the lt_bw a
> bit later.
> 
> This commit is a stable candidate for kernels back as far as 4.9.
> 
> Fixes: 0f8782ea1497 ("tcp_bbr: add BBR congestion control")
> Signed-off-by: Neal Cardwell <ncardwell@google.com>
> Signed-off-by: Yuchung Cheng <ycheng@google.com>
> Signed-off-by: Soheil Hassas Yeganeh <soheil@google.com>
> Reported-by: Beyers Cronje <bcronje@gmail.com>

Applied and queued up for -stable, thanks Neal.

      reply	other threads:[~2018-02-01 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 20:43 [PATCH net] tcp_bbr: fix pacing_gain to always be unity when using lt_bw Neal Cardwell
2018-02-01 14:44 ` David Miller [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=20180201.094422.1284279400896772062.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=soheil@google.com \
    --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).