From: Eric Dumazet <eric.dumazet@gmail.com>
To: Yuchung Cheng <ycheng@google.com>
Cc: davem@davemloft.net, ncardwell@google.com, edumazet@google.com,
nanditad@google.com, ilpo.jarvinen@cs.helsinki.fi,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 3/3 net-next] tcp: implement RFC5682 F-RTO
Date: Wed, 20 Mar 2013 22:00:32 -0700 [thread overview]
Message-ID: <1363842032.3333.48.camel@edumazet-glaptop> (raw)
In-Reply-To: <1363822380-16687-3-git-send-email-ycheng@google.com>
On Wed, 2013-03-20 at 16:33 -0700, Yuchung Cheng wrote:
> This patch implements F-RTO (foward RTO recovery):
>
> When the first retransmission after timeout is acknowledged, F-RTO
> sends new data instead of old data. If the next ACK acknowledges
> some never-retransmitted data, then the timeout was spurious and the
> congestion state is reverted. Otherwise if the next ACK selectively
> acknowledges the new data, then the timeout was genuine and the
> loss recovery continues. This idea applies to recurring timeouts
> as well. While F-RTO sends different data during timeout recovery,
> it does not (and should not) change the congestion control.
>
> The implementaion follows the three steps of SACK enhanced algorithm
> (section 3) in RFC5682. Step 1 is in tcp_enter_loss(). Step 2 and
> 3 are in tcp_process_loss(). The basic version is not supported
> because SACK enhanced version also works for non-SACK connections.
>
> The new implementation is functionally in parity with the old F-RTO
> implementation except the one case where it increases undo events:
> In addition to the RFC algorithm, a spurious timeout may be detected
> without sending data in step 2, as long as the SACK confirms not
> all the original data are dropped. When this happens, the sender
> will undo the cwnd and perhaps enter fast recovery instead. This
> additional check increases the F-RTO undo events by 5x compared
> to the prior implementation on Google Web servers, since the sender
> often does not have new data to send for HTTP.
>
> Note F-RTO may detect spurious timeout before Eifel with timestamps
> does so.
>
> Signed-off-by: Yuchung Cheng <ycheng@google.com>
> ---
> ChangeLog in v2:
> - Removed extra while spaces
> - Allow F-RTO in sack reneging case to detect spurious retransmit(s)
> - Re-tested after merging with the recent TCP tail loss probe patch
>
> Documentation/networking/ip-sysctl.txt | 18 +++------
> include/linux/tcp.h | 3 +-
> net/ipv4/tcp_input.c | 73 ++++++++++++++++++++++++++++------
> 3 files changed, 68 insertions(+), 26 deletions(-)
Acked-by: Eric Dumazet <edumazet@google.com>
next prev parent reply other threads:[~2013-03-21 5:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 23:32 [PATCH v2 1/3 net-next] tcp: refactor F-RTO Yuchung Cheng
2013-03-20 23:32 ` [PATCH v2 2/3 net-next] tcp: refactor CA_Loss state processing Yuchung Cheng
2013-03-20 23:56 ` Eric Dumazet
2013-03-20 23:33 ` [PATCH v2 3/3 net-next] tcp: implement RFC5682 F-RTO Yuchung Cheng
2013-03-21 5:00 ` Eric Dumazet [this message]
2013-03-21 13:26 ` Neal Cardwell
2013-03-20 23:55 ` [PATCH v2 1/3 net-next] tcp: refactor F-RTO Eric Dumazet
2013-03-21 15:48 ` David Miller
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=1363842032.3333.48.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ilpo.jarvinen@cs.helsinki.fi \
--cc=nanditad@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