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, edumazet@google.com
Subject: Re: [PATCH net] tcp_yeah: don't set ssthresh below 2
Date: Mon, 11 Jan 2016 17:25:48 -0500 (EST)	[thread overview]
Message-ID: <20160111.172548.746102330510579400.davem@davemloft.net> (raw)
In-Reply-To: <1452537763-28163-1-git-send-email-ncardwell@google.com>

From: Neal Cardwell <ncardwell@google.com>
Date: Mon, 11 Jan 2016 13:42:43 -0500

> For tcp_yeah, use an ssthresh floor of 2, the same floor used by Reno
> and CUBIC, per RFC 5681 (equation 4).
> 
> tcp_yeah_ssthresh() was sometimes returning a 0 or negative ssthresh
> value if the intended reduction is as big or bigger than the current
> cwnd. Congestion control modules should never return a zero or
> negative ssthresh. A zero ssthresh generally results in a zero cwnd,
> causing the connection to stall. A negative ssthresh value will be
> interpreted as a u32 and will set a target cwnd for PRR near 4
> billion.
> 
> Oleksandr Natalenko reported that a system using tcp_yeah with ECN
> could see a warning about a prior_cwnd of 0 in
> tcp_cwnd_reduction(). Testing verified that this was due to
> tcp_yeah_ssthresh() misbehaving in this way.
> 
> Reported-by: Oleksandr Natalenko <oleksandr@natalenko.name>
> Signed-off-by: Neal Cardwell <ncardwell@google.com>
> Signed-off-by: Yuchung Cheng <ycheng@google.com>
> Signed-off-by: Eric Dumazet <edumazet@google.com>

Applied and queued up for -stable, thanks!

      reply	other threads:[~2016-01-11 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 18:42 [PATCH net] tcp_yeah: don't set ssthresh below 2 Neal Cardwell
2016-01-11 22:25 ` 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=20160111.172548.746102330510579400.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=edumazet@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).