From: David Miller <davem@davemloft.net>
To: amwang@redhat.com
Cc: netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru, kaber@trash.net,
edumazet@google.com, nhorman@tuxdriver.com
Subject: Re: [RFC PATCH net-next] tcp: introduce tcp_tw_interval to specifiy the time of TIME-WAIT
Date: Thu, 27 Sep 2012 13:05:29 -0400 (EDT) [thread overview]
Message-ID: <20120927.130529.620560818048014548.davem@davemloft.net> (raw)
In-Reply-To: <1348735261-29225-1-git-send-email-amwang@redhat.com>
From: Cong Wang <amwang@redhat.com>
Date: Thu, 27 Sep 2012 16:41:01 +0800
> In commercial Unix systems, this kind of parameters, such as
> tcp_timewait in AIX and tcp_time_wait_interval in HP-UX, have
> already been available. Their implementations allow users to tune
> how long they keep TCP connection as TIME-WAIT state on the
> millisecond time scale."
This statement only makes me happy that these systems are not as
widely deployed as Linux is.
Furthermore, the mere existence of a facility in another system
is never an argument for why we should have it too. Often it's
instead a huge reason for us not to add it.
Without appropriate confirmation that an early time-wait reuse is
valid, decreasing this interval can only be dangerous.
next prev parent reply other threads:[~2012-09-27 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 8:41 [RFC PATCH net-next] tcp: introduce tcp_tw_interval to specifiy the time of TIME-WAIT Cong Wang
2012-09-27 14:23 ` Neil Horman
2012-09-27 17:02 ` Rick Jones
2012-09-28 6:33 ` Cong Wang
2012-09-28 6:43 ` David Miller
2012-09-28 17:30 ` Rick Jones
2012-09-28 13:16 ` Neil Horman
2012-10-02 7:04 ` Cong Wang
2012-10-02 12:09 ` Neil Horman
2012-10-08 3:17 ` Cong Wang
2012-10-08 14:07 ` Neil Horman
2012-10-09 3:42 ` Cong Wang
2012-09-27 17:05 ` David Miller [this message]
2012-09-28 6:39 ` Cong Wang
2012-09-28 6:44 ` David Miller
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=20120927.130529.620560818048014548.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amwang@redhat.com \
--cc=edumazet@google.com \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/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).