From: David Miller <davem@davemloft.net>
To: ilpo.jarvinen@helsinki.fi
Cc: damian@tvk.rwth-aachen.de, netdev@vger.kernel.org
Subject: Re: [PATCH][v4] tcp: fix ICMP-RTO war
Date: Sun, 21 Feb 2010 18:10:29 -0800 (PST) [thread overview]
Message-ID: <20100221.181029.71107197.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1002151535030.7063@wel-95.cs.helsinki.fi>
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Date: Tue, 16 Feb 2010 14:45:25 +0200 (EET)
> On Wed, 10 Feb 2010, Damian Lukowski wrote:
>
>> @@ -5783,12 +5783,10 @@ int tcp_rcv_state_process(struct sock *sk, struct sk_buff *skb,
>>
>> /* tcp_ack considers this ACK as duplicate
>> * and does not calculate rtt.
>> - * Fix it at least with timestamps.
>> + * Force it here.
>> */
>> - if (tp->rx_opt.saw_tstamp &&
>> - tp->rx_opt.rcv_tsecr && !tp->srtt)
>> - tcp_ack_saw_tstamp(sk, 0);
>> -
>> + tcp_ack_update_rtt(sk, 0, 0);
>> +
>
> ...Here a zero seq_rtt is given to RTT estimator (it will be effective
> only in the case w/o timestamps, TS case recalculates it from the stored
> timestamps). Maybe we could use some field (timestamp related one comes to
> my mind) in request sock to get a real RTT estimate for non-timestamp case
> too. ...It seems possible to me, though tricky because the request_sock is
> no longer that easily available here so some parameter passing would be
> needed.
Agreed.
But even more simply I think we should make even the current
tcp_ack_update_rtt() call here conditional on at least
tp->srtt being zero.
Damian do you at least agree with that?
next prev parent reply other threads:[~2010-02-22 2:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 19:06 [PATCH][v4] tcp: fix ICMP-RTO war Damian Lukowski
2010-02-10 19:08 ` David Miller
2010-02-11 2:04 ` David Miller
2010-02-16 12:45 ` Ilpo Järvinen
2010-02-22 2:10 ` David Miller [this message]
[not found] ` <o2z349f35ee1005071622z38fcd66ek398402d7512542ae@mail.gmail.com>
2010-05-07 23:25 ` Jerry Chu
2010-05-08 8:30 ` Damian Lukowski
2010-05-08 17:27 ` Jerry Chu
2010-05-08 22:00 ` 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=20100221.181029.71107197.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=damian@tvk.rwth-aachen.de \
--cc=ilpo.jarvinen@helsinki.fi \
--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).