From: Eric Dumazet <eric.dumazet@gmail.com>
To: Alexander Bergmann <alex@linlab.net>
Cc: davem@davemloft.net, hkjerry.chu@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] tcp: Wrong timeout for SYN segments
Date: Fri, 31 Aug 2012 06:25:50 -0700 [thread overview]
Message-ID: <1346419550.2591.12.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120831124831.GA23279@linlab.net>
On Fri, 2012-08-31 at 14:48 +0200, Alexander Bergmann wrote:
> Hi Eric!
>
> I've also changed the Documentation file. As usual, comments are welcome!
>
>
> Alex
>
>
> From 848f34ce27f65401940ae98e0b2d395888d3986d Mon Sep 17 00:00:00 2001
> From: Alexander Bergmann <alex@linlab.net>
> Date: Fri, 31 Aug 2012 14:31:00 +0200
> Subject: [PATCH 1/1] tcp: Increase timeout for SYN segments
>
> Commit 9ad7c049 changed the initRTO from 3secs to 1sec in accordance to
> RFC6298 (former RFC2988bis). This reduced the time till the last SYN
> retransmission packet gets sent from 93secs to 31secs.
>
> RFC1122 is stating that the retransmission should be done for at least 3
> minutes, but this seems to be quite high.
>
> "However, the values of R1 and R2 may be different for SYN
> and data segments. In particular, R2 for a SYN segment MUST
> be set large enough to provide retransmission of the segment
> for at least 3 minutes. The application can close the
> connection (i.e., give up on the open attempt) sooner, of
> course."
>
> This patch increases the value of TCP_SYN_RETRIES to the value of 6,
> providing a retransmission window of 63secs.
>
> The comments for SYN and SYNACK retries have also been updated to
> describe the current settings. The same goes for the documentation file
> "Documentation/networking/ip-sysctl.txt".
>
> Signed-off-by: Alexander Bergmann <alex@linlab.net>
> ---
Thanks for your patience and followup, this seems good to me !
Acked-by: Eric Dumazet <edumazet@google.com>
next prev parent reply other threads:[~2012-08-31 13:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 23:29 [PATCH 1/1] tcp: Wrong timeout for SYN segments Alex Bergmann
2012-08-22 8:06 ` Eric Dumazet
2012-08-22 8:48 ` Alex Bergmann
2012-08-22 8:58 ` Eric Dumazet
2012-08-22 9:29 ` Alex Bergmann
2012-08-22 9:59 ` Eric Dumazet
2012-08-22 10:03 ` Eric Dumazet
2012-08-22 17:29 ` H.K. Jerry Chu
2012-08-22 16:44 ` H.K. Jerry Chu
[not found] ` <CAFbMe2M7ekc94bQk7vTS1LhScPd49VZ-zKOCUXhqwxXtL-nkuA@mail.gmail.com>
2012-08-23 11:58 ` Alex Bergmann
2012-08-23 12:15 ` Eric Dumazet
2012-08-23 12:35 ` David Laight
2012-08-23 12:51 ` Eric Dumazet
2012-08-23 12:37 ` Alex Bergmann
2012-08-23 12:49 ` Eric Dumazet
2012-08-24 12:17 ` Alex Bergmann
2012-08-24 17:42 ` David Miller
2012-08-25 8:48 ` Alexander Bergmann
2012-08-25 9:01 ` Eric Dumazet
2012-08-28 8:44 ` Carsten Wolff
[not found] ` <1346414260.2591.8.camel@edumazet-glaptop>
2012-08-31 12:48 ` Alexander Bergmann
2012-08-31 13:25 ` Eric Dumazet [this message]
2012-08-31 19:42 ` David Miller
2012-08-31 19:47 ` David Miller
2012-08-29 4:34 ` H.K. Jerry Chu
2012-08-29 8:51 ` Eric Dumazet
2012-08-29 17:25 ` H.K. Jerry Chu
2012-08-30 13:12 ` Eric Dumazet
2012-08-30 16:45 ` David Miller
2012-08-30 18:04 ` H.K. Jerry Chu
2012-08-30 17:59 ` H.K. Jerry Chu
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=1346419550.2591.12.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=alex@linlab.net \
--cc=davem@davemloft.net \
--cc=hkjerry.chu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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