From: Andi Kleen <andi@firstfloor.org>
To: David Miller <davem@davemloft.net>
Cc: paulsheer@gmail.com, linux-kernel@vger.kernel.org,
roque@di.fc.ul.pt, netdev@vger.kernel.org
Subject: Re: TCP kernel tables overflowing after sustained 1000 new connections per second
Date: Thu, 10 Sep 2009 11:24:04 +0200 [thread overview]
Message-ID: <87k5075f0r.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20090909.170824.141343404.davem@davemloft.net> (David Miller's message of "Wed, 09 Sep 2009 17:08:24 -0700 (PDT)")
> On a gigabit local LAN I can set the timeouts very low to encourage
> port reuse. A well known configuration issue with all OS's - just search
> for MyOS+TIMED_WAIT on google. No problems here.
The timeouts are what they are for a reason to detect old packets in
the network and prevent data corruption. That's why the RFCs require
them.
Unless you never run on WANs or have very strong data integry checking
in your application (e.g. SSL) it's normally not a good idea to mess
with them.
When you run out of port space you should use more local IP addresses.
Possibly if you don't have problems with firewalls you could
also increase the port space, but that's still limited.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-09-10 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 18:46 TCP kernel tables overflowing after sustained 1000 new connections per second Paul Sheer
2009-09-09 19:16 ` Chuck Ebbert
2009-09-10 0:08 ` David Miller
2009-09-10 0:26 ` Brian Haley
2009-09-10 9:24 ` Andi Kleen [this message]
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=87k5075f0r.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulsheer@gmail.com \
--cc=roque@di.fc.ul.pt \
/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