From: David Miller <davem@davemloft.net>
To: ycheng@google.com
Cc: netdev@vger.kernel.org, ncardwell@google.com, edumazet@google.com
Subject: Re: [PATCH net] tcp: avoid cwnd undo after receiving ECN
Date: Fri, 29 Jan 2016 23:04:19 -0800 (PST) [thread overview]
Message-ID: <20160129.230419.1854358229164635050.davem@davemloft.net> (raw)
In-Reply-To: <1454109110-32068-1-git-send-email-ycheng@google.com>
From: Yuchung Cheng <ycheng@google.com>
Date: Fri, 29 Jan 2016 15:11:50 -0800
> RFC 4015 section 3.4 says the TCP sender MUST refrain from
> reversing the congestion control state when the ACK signals
> congestion through the ECN-Echo flag. Currently we may not
> always do that when prior_ssthresh is reset upon receiving
> ACKs with ECE marks. This patch fixes that.
>
> Signed-off-by: Yuchung Cheng <ycheng@google.com>
> Signed-off-by: Neal Cardwell <ncardwell@google.com>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Applied, thanks.
prev parent reply other threads:[~2016-01-30 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 23:11 [PATCH net] tcp: avoid cwnd undo after receiving ECN Yuchung Cheng
2016-01-30 7:04 ` 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=20160129.230419.1854358229164635050.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).