From: Rick Jones <rick.jones2@hp•com>
To: Cong Wang <amwang@redhat•com>
Cc: Neil Horman <nhorman@tuxdriver•com>,
netdev@vger•kernel.org, "David S. Miller" <davem@davemloft•net>,
Alexey Kuznetsov <kuznet@ms2•inr.ac.ru>,
Patrick McHardy <kaber@trash•net>,
Eric Dumazet <edumazet@google•com>
Subject: Re: [RFC PATCH net-next] tcp: introduce tcp_tw_interval to specifiy the time of TIME-WAIT
Date: Thu, 27 Sep 2012 10:02:22 -0700 [thread overview]
Message-ID: <5064869E.9060503@hp.com> (raw)
In-Reply-To: <20120927142334.GA3194@neilslaptop.think-freely.org>
On 09/27/2012 07:23 AM, Neil Horman wrote:
> The code looks fine, but the idea really doesn't seem like a good plan to me.
> I'm sure HPUX/Solaris/AIX/etc have done this in response to customer demand, but
> that doesn't make it the right solution.
In the case of HP-UX at least, while the rope is indeed there, the
advice is to not wrap it around one's neck unless one *really* has a
handle on the environment. Instead things suggested, in no particular
order:
*) The aforementioned SO_REUSEADDR to address the "I can't restart the
server quickly enough." issue
*) Tuning the size of the anonymous/ephemeral port range.
*) Making explicit bind() calls using the entire non-privileged port range
*) Making the connections longer-lived. Especially if the comms are
between a fixed set of IP addresses.
rick jones
next prev parent reply other threads:[~2012-09-27 17:02 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 [this message]
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
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=5064869E.9060503@hp.com \
--to=rick.jones2@hp$(echo .)com \
--cc=amwang@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=kaber@trash$(echo .)net \
--cc=kuznet@ms2$(echo .)inr.ac.ru \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nhorman@tuxdriver$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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