From: Neal Cardwell <ncardwell@google.com>
To: Nandita Dukkipati <nanditad@google.com>
Cc: "Eric Dumazet" <eric.dumazet@gmail.com>,
"Per Hurtig" <per.hurtig@kau.se>,
panweiping3@gmail.com, Netdev <netdev@vger.kernel.org>,
"Anna Brunström" <anna.brunstrom@kau.se>,
mohammad.rajiullah@kau.se, sergei.shtylyov@cogentembedded.com
Subject: Re: [PATCH v2 1/1] tcp: fixing TLP's FIN recovery
Date: Thu, 12 Jun 2014 13:46:50 -0400 [thread overview]
Message-ID: <CADVnQymKHsd4HD-vJgTEhf2L_5Trae-Peo4Z4be2k5MhenC6+g@mail.gmail.com> (raw)
In-Reply-To: <CAB_+Fg69Ub-AQn3FyvcGTq7PQK9Lxi=zF8xPW+f4Qjhr6oJ+JA@mail.gmail.com>
On Thu, Jun 12, 2014 at 1:36 PM, Nandita Dukkipati <nanditad@google.com> wrote:
> On Thu, Jun 12, 2014 at 8:28 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>> On Thu, 2014-06-12 at 17:08 +0200, Per Hurtig wrote:
>>> Fix to a problem observed when losing a FIN segment that does not
>>> contain data. In such situations, TLP is unable to recover from
>>> *any* tail loss and instead adds at least PTO ms to the
>>> retransmission process, i.e., RTO = RTO + PTO.
>>>
>>> Signed-off-by: Per Hurtig <per.hurtig@kau.se>
>>> ---
>>> net/ipv4/tcp_output.c | 4 +---
>>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>>
>>> diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
>>> index ad7549f..819bf0c 100644
>>> --- a/net/ipv4/tcp_output.c
>>> +++ b/net/ipv4/tcp_output.c
>>> @@ -2131,9 +2131,7 @@ void tcp_send_loss_probe(struct sock *sk)
>>> if (WARN_ON(!skb || !tcp_skb_pcount(skb)))
>>> goto rearm_timer;
>>>
>>> - /* Probe with zero data doesn't trigger fast recovery. */
>>> - if (skb->len > 0)
>>> - err = __tcp_retransmit_skb(sk, skb);
>>> + err = __tcp_retransmit_skb(sk, skb);
>>>
>>> /* Record snd_nxt for loss detection. */
>>> if (likely(!err))
>>
>> Thanks a lot Per
>>
>> Signed-off-by: Eric Dumazet <edumazet@google.com>
>
> Acked-by: Nandita Dukkipati <nanditad@google.com>
Thanks, Per!
Acked-by: Neal Cardwell <ncardwell@google.com>
neal
next prev parent reply other threads:[~2014-06-12 17:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 18:46 tcp: fixing TLP's FIN recovery Per Hurtig
2014-06-06 19:07 ` Eric Dumazet
2014-06-07 11:10 ` [PATCH] " Per Hurtig
2014-06-07 13:56 ` Sergei Shtylyov
2014-06-07 14:34 ` Per Hurtig
2014-06-08 2:58 ` Eric Dumazet
2014-06-08 7:41 ` Per Hurtig
2014-06-08 16:35 ` Eric Dumazet
2014-06-09 7:04 ` Nandita Dukkipati
2014-06-09 7:02 ` Nandita Dukkipati
2014-06-09 13:13 ` Per Hurtig
2014-06-09 14:33 ` Eric Dumazet
2014-06-09 14:39 ` Eric Dumazet
2014-06-09 14:42 ` Per Hurtig
2014-06-09 15:04 ` Eric Dumazet
2014-06-09 15:56 ` Per Hurtig
2014-06-09 16:15 ` Eric Dumazet
2014-06-09 16:24 ` Eric Dumazet
2014-06-09 18:33 ` Eric Dumazet
2014-06-12 14:21 ` Weiping Pan
2014-06-12 14:32 ` Eric Dumazet
2014-06-12 15:08 ` [PATCH v2 1/1] " Per Hurtig
2014-06-12 15:28 ` Eric Dumazet
2014-06-12 17:36 ` Nandita Dukkipati
2014-06-12 17:46 ` Neal Cardwell [this message]
2014-06-12 18:06 ` David Miller
2014-10-07 15:03 ` Josh Hunt
2014-10-07 20:17 ` 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=CADVnQymKHsd4HD-vJgTEhf2L_5Trae-Peo4Z4be2k5MhenC6+g@mail.gmail.com \
--to=ncardwell@google.com \
--cc=anna.brunstrom@kau.se \
--cc=eric.dumazet@gmail.com \
--cc=mohammad.rajiullah@kau.se \
--cc=nanditad@google.com \
--cc=netdev@vger.kernel.org \
--cc=panweiping3@gmail.com \
--cc=per.hurtig@kau.se \
--cc=sergei.shtylyov@cogentembedded.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).