netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ncardwell@google.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: ecn: dont delay ACKS after CE
Date: Mon, 06 Aug 2012 14:14:51 -0700 (PDT)	[thread overview]
Message-ID: <20120806.141451.191138983583413911.davem@davemloft.net> (raw)
In-Reply-To: <CADVnQyk25R4qpXq7Mho=uHwCswALPdOR=nP=AjQy7qJyT+HFuA@mail.gmail.com>

From: Neal Cardwell <ncardwell@google.com>
Date: Mon, 6 Aug 2012 17:07:08 -0400

> On Mon, Aug 6, 2012 at 5:04 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>> From: Eric Dumazet <edumazet@google.com>
>>
>> While playing with CoDel and ECN marking, I discovered a
>> non optimal behavior of receiver of CE (Congestion Encountered)
>> segments.
>>
>> In pathological cases, sender has reduced its cwnd to low values,
>> and receiver delays its ACK (by 40 ms).
>>
>> While RFC 3168 6.1.3 (The TCP Receiver) doesn't explicitly recommend
>> to send immediate ACKS, we believe its better to not delay ACKS, because
>> a CE segment should give same signal than a dropped segment, and its
>> quite important to reduce RTT to give ECE/CWR signals as fast as
>> possible.
>>
>> Note we already call tcp_enter_quickack_mode() from TCP_ECN_check_ce()
>> if we receive a retransmit, for the same reason.
>>
>> Signed-off-by: Eric Dumazet <edumazet@google.com>
>> Cc: Neal Cardwell <ncardwell@google.com>
> 
> Acked-by: Neal Cardwell <ncardwell@google.com>

Applied, thanks.

      reply	other threads:[~2012-08-06 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 21:04 [PATCH net-next] tcp: ecn: dont delay ACKS after CE Eric Dumazet
2012-08-06 21:07 ` Neal Cardwell
2012-08-06 21:14   ` 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=20120806.141451.191138983583413911.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    /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).