netdev
[Top] [All Lists]

Re: A question on RTT estimation of SACKed packet.

To: weixl@xxxxxxxxxxx (Xiaoliang \(David\), Wei)
Subject: Re: A question on RTT estimation of SACKed packet.
From: kuznet@xxxxxxxxxxxxx
Date: Thu, 29 Aug 2002 23:01:11 +0400 (MSD)
Cc: netdev@xxxxxxxxxxx
In-reply-to: <037601c24f45$4549fe10$f1fa010a@weixl> from "Xiaoliang \(David\) Wei" at Aug 29, 2 02:45:00 pm
Sender: netdev-bounce@xxxxxxxxxxx
Hello!

>     2. When a packet was SACKed but not retransmitted, the linux also
> calculate the seq_rtt from it when there is no unSACKed packet in the queue.
>      I cannot understand the second situation: The packet was SACKed before,
> that means it arrived the receiver and triggered a SACK sometime before. The
> interval between when packet is sent and when the SACK is received should be
> the RTT for experienced this packet. Even now the packet is ACKed, I don't
> think this ACK is triggered by this packet. Why is it used to calculate the
> RTT?

It is not used. When a segment fills a hole, tcp uses skb->when of the segment
which _filled_ the hole. See?

What's about using SACKs to give additional feed to rtt estimator,
even when ACK is duplicate, it is intersting idea, I even read about
this somewhere. But we do not use this.

Alexey

<Prev in Thread] Current Thread [Next in Thread>