[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1206042116560.17280@melkinpaasi.cs.helsinki.fi>
Date: Mon, 4 Jun 2012 22:18:19 +0300 (EEST)
From: "Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To: Damian Lukowski <damian@....rwth-aachen.de>
cc: Jerry Chu <hkchu@...gle.com>, Netdev <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH 3/3] Revert Backoff [v3]: Calculate TCP's connection
close threshold as a time value.
On Mon, 4 Jun 2012, Damian Lukowski wrote:
> please verify, I understood you correctly.
>
> You have set TCP_RTO_MIN to a lower value, e.g. 0.002 seconds to improve
> your internal low-latency traffic. Because of the improvement, R1
> timeouts are triggered too fast for external high-RTT traffic. Is that
> correct?
> If so, may I suggest to set tcp_retries1 to a higher value? For
> TCP_RTO_MIN == 0.002 and tcp_retries1 == 10, R1 will be calculated to
> approximately 4 seconds.
>
> Is that ok?
I suppose what he meant is that you could have e.g., 60sec RTT and with
small enough retries the timeout calculation yields to some timeout
smaller than 60 secs, and therefore no retransmissions are made which is
certainly not a desirable property? ...This is valid issue even if no min
rto tweaking was done but can of course get much worse if min rto is
shorter.
I agree with his proposed solution:
> > I think retransmits_timed_out() should check against both time
> > duration and retrans count (icsk_retransmits).
...that is, use both pseudo timeout check of the current code and the
previously used icsk_retransmits compare at the same time.
--
i.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists