From: David Miller <davem@davemloft.net>
To: yavor@simplifymedia.com
Cc: netdev@vger.kernel.org
Subject: Re: [Patch] Establishing more than 64K outgoing TCP connections
Date: Sat, 01 Nov 2008 21:15:41 -0700 (PDT) [thread overview]
Message-ID: <20081101.211541.182428064.davem@davemloft.net> (raw)
In-Reply-To: <241CE5A1B2AFFA4987A663380D74C0BB3FD69B08A7@MBX73.ad2.softcom.biz>
From: Yavor Goulishev <yavor@simplifymedia.com>
Date: Tue, 28 Oct 2008 17:06:33 -0400
> I'm sending you a tiny patch for the kernel. The change allowed me
> to establish more than 64K outgoing TCP connections from a single
> Linux box. Being able to use multihomed client box to load test a
> server reduced dramatically the number of physical boxes I needed.
> The other way to go was virtual machines, but you can't beat the
> simplicity of the single multihomed client. Also the patch fixes an
> important symmetry. Using the multihome setup is a simple technique
> to overcome the 64K limit on the server side. The patch makes it
> possible on the client side too.
>
> The fix is only for TCP but probably the same issue exists for UDP.
> I didn't had the time to investigate.
>
> The patch is against the latest code base 2.6.28-rc2.
As I mentioned in my initial reply to you, this exact patch
has been proposed in the future and rejected.
The problem is that although it fixes the limitation, it
introduces a new problem.
The current code tries to keep the hash chains as shallow
as possible. One part of how it achieves this is that it
tries to use up all the available ports using it's
scanning algorithm. Your change works against this, and
will tend to make the hash chains deeper.
A solution needs to be devised which handles both issues.
next prev parent reply other threads:[~2008-11-02 4:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 21:06 [Patch] Establishing more than 64K outgoing TCP connections Yavor Goulishev
2008-11-02 4:15 ` David Miller [this message]
2008-11-07 6:12 ` Yavor Goulishev
2008-11-07 6:23 ` David Miller
2008-11-07 6:57 ` Yavor Goulishev
2008-11-07 7:04 ` David Miller
2008-11-07 7:15 ` Yavor Goulishev
2008-11-07 7:30 ` David Miller
2008-11-07 7:40 ` Yavor Goulishev
2008-11-07 8:45 ` Evgeniy Polyakov
2008-11-07 16:38 ` Yavor Goulishev
2008-11-07 17:25 ` Evgeniy Polyakov
2008-11-07 19:54 ` David Miller
2008-11-07 22:37 ` Yavor Goulishev
2008-11-07 23:04 ` Evgeniy Polyakov
2008-11-07 8:36 ` Rémi Denis-Courmont
2008-11-07 15:56 ` Yavor Goulishev
2008-11-07 16:23 ` Eric Dumazet
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=20081101.211541.182428064.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yavor@simplifymedia.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).