From: Li Yu <raise.sail@gmail.com>
To: Chao Pei <peichao85@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: a F-RTO question
Date: Wed, 28 Mar 2012 12:08:41 +0800 [thread overview]
Message-ID: <4F728EC9.1050302@gmail.com> (raw)
In-Reply-To: <CAJkE24+qgK4_cGtiEi6hWDFS2EVYPajHY3pigwh_RqguwsedNg@mail.gmail.com>
于 2012年03月28日 11:49, Chao Pei 写道:
>> Hi,
>>
>> I have a question about tcp_process_frto(), the below source
>> code :
>>
>> static int tcp_process_frto(struct sock *sk, int flag)
>> {
>> .....
>>
>> if (!before(tp->snd_una, tp->frto_highmark)) {
>> tcp_enter_frto_loss(sk, ...);
>> return 1;
>> }
>>
>> .....
>>
>> }
>>
>> As my understanding, the tp->frto_highmark likes tp->high_seq,
>> it saves the seqno SND_NXT when a TCP connection enters F-RTO phase,
>> is it the variable "recovery" in NewReno? So I think that if snd_una is
>> equal with or after frto_highmark, which means peer ack new data, so
>> why we enter Loss state here?
>>
>> Thanks!
>>
>> Yu
>>
>>
>
> If snd_una advances to frto_highmark, it is likely that the hole was
> filled by the retransimitted packet, which means the original packet
> was likely to have been lost.
> So, we should enter loss state.
>
I do not agree with it, if snd_una advanced to frto_highmark, which
means peer acks whole window of data instead of just one segment, and
we can not make sure that reason of peer sends ack is whether it
received original segment or retransmitted segment.
Even, the reason is latter, it also means the netowrk already is
recovered from temporarily congestion or disordered state, so we also
should not enter loss state.
Thanks
Yu
next prev parent reply other threads:[~2012-03-28 4:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 3:13 a F-RTO question Li Yu
2012-03-28 3:49 ` Chao Pei
2012-03-28 4:08 ` Li Yu [this message]
2012-03-28 5:27 ` Chao Pei
2012-03-28 5:35 ` Yuchung Cheng
2012-03-28 6:43 ` Li Yu
2012-04-10 8:34 ` Ilpo Järvinen
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=4F728EC9.1050302@gmail.com \
--to=raise.sail@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peichao85@gmail.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).