From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: Alex Bergmann <alex@linlab.net>,
"H.K. Jerry Chu" <hkjerry.chu@gmail.com>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: RE: [PATCH 1/1] tcp: Wrong timeout for SYN segments
Date: Thu, 23 Aug 2012 14:51:23 +0200 [thread overview]
Message-ID: <1345726283.5904.842.camel@edumazet-glaptop> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B6FC3@saturn3.aculab.com>
On Thu, 2012-08-23 at 13:35 +0100, David Laight wrote:
> > I would suggest to increase TCP_SYN_RETRIES from 5 to 6.
> >
> > 180 secs is eternity, but 31 secs is too small.
>
> Wasn't the intention of the long delay to allow a system
> acting as a router to reboot?
> I suspect that is why it (and some other TCP timers)
> are in minutes.
One could argue that if an application really wants to connect to a
peer, it should probably handle failures and retries.
But for unaware (basic ?) applications, the 3 -> 1 change reduced by a 3
factor the timeout. So a transient network failure has now more
chance to impact them.
Not all applications run inside a browser or under human control...
next prev parent reply other threads:[~2012-08-23 12:51 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 [this message]
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
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=1345726283.5904.842.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=David.Laight@ACULAB.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;
as well as URLs for NNTP newsgroup(s).