From: David Miller <davem@davemloft.net>
To: yuri@itinteg.net
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, damian@tvk.rwth-aachen.de
Subject: Re: [Bugme-new] [Bug 18952] New: The mount of SYN retries is not equal to /proc/sys/net/ipv4/tcp_syn_retries
Date: Mon, 27 Sep 2010 01:10:46 -0700 (PDT) [thread overview]
Message-ID: <20100927.011046.45906887.davem@davemloft.net> (raw)
In-Reply-To: <201009271007.06705.yuri@itinteg.net>
From: Yuri Chislov <yuri@itinteg.net>
Date: Mon, 27 Sep 2010 10:07:06 +0200
> It looks like the behavior changed in 2.6.32. 2.6.32 and up, uses some
> calculation instead of a direct definition of the retries number, that makes it
> harder to achieve the necessary system behavior.
>
> The default behavior of the system changed completely
> (the old default connect timeout was ~ 180 seconds, while the new one is ~21
> sec).
>
> The new behavior invalidates the kernel documentation and tcp man page.
>
> It's not possible to set a connect timeout > 25 sec in the applications while
> using the default values in /proc.
>
> From my view point is regression.
Agreed, Damian you have to fix this.
Otherwise I'm reverting all of your Revert Backoff commits.
next prev parent reply other threads:[~2010-09-27 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18952-10286@https.bugzilla.kernel.org/>
2010-09-22 9:02 ` [Bugme-new] [Bug 18952] New: The mount of SYN retries is not equal to /proc/sys/net/ipv4/tcp_syn_retries Andrew Morton
2010-09-25 3:05 ` David Miller
2010-09-27 8:07 ` Yuri Chislov
2010-09-27 8:10 ` David Miller [this message]
2010-09-27 8:35 ` Damian Lukowski
2010-09-27 20:00 ` Damian Lukowski
2010-09-28 4:52 ` David Miller
2010-09-28 7:40 ` Yuri Chislov
2010-09-28 9:47 ` Ilpo Järvinen
2010-09-28 12:08 ` Yuri Chislov
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=20100927.011046.45906887.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=damian@tvk.rwth-aachen.de \
--cc=netdev@vger.kernel.org \
--cc=yuri@itinteg.net \
/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).