From: David Miller <davem@davemloft.net>
To: ncardwell@google.com
Cc: netdev@vger.kernel.org, ycheng@google.com, soheil@google.com,
priyarjha@google.com, ysseung@google.com
Subject: Re: [PATCH net] tcp_bbr: fix to zero idle_restart only upon S/ACKed data
Date: Wed, 02 May 2018 11:13:07 -0400 (EDT) [thread overview]
Message-ID: <20180502.111307.1740648414339763049.davem@davemloft.net> (raw)
In-Reply-To: <20180502014541.194259-1-ncardwell@google.com>
From: Neal Cardwell <ncardwell@google.com>
Date: Tue, 1 May 2018 21:45:41 -0400
> Previously the bbr->idle_restart tracking was zeroing out the
> bbr->idle_restart bit upon ACKs that did not SACK or ACK anything,
> e.g. receiving incoming data or receiver window updates. In such
> situations BBR would forget that this was a restart-from-idle
> situation, and if the min_rtt had expired it would unnecessarily enter
> PROBE_RTT (even though we were actually restarting from idle but had
> merely forgotten that fact).
>
> The fix is simple: we need to remember we are restarting from idle
> until we receive a S/ACK for some data (a S/ACK for the first flight
> of data we send as we are restarting).
>
> 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>
> Signed-off-by: Priyaranjan Jha <priyarjha@google.com>
> Signed-off-by: Yousuk Seung <ysseung@google.com>
Applied and queued up for -stable.
prev parent reply other threads:[~2018-05-02 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 1:45 [PATCH net] tcp_bbr: fix to zero idle_restart only upon S/ACKed data Neal Cardwell
2018-05-02 15:13 ` 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=20180502.111307.1740648414339763049.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=priyarjha@google.com \
--cc=soheil@google.com \
--cc=ycheng@google.com \
--cc=ysseung@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