On 7/4/07, Eric Dumazet <[EMAIL PROTECTED]> wrote:
On Wed, 4 Jul 2007 11:40:48 +0200
"Robert Iakobashvili" <[EMAIL PROTECTED]> wrote:
> On 7/4/07, Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> > On Wed, Jul 04, 2007 at 09:50:31AM +0200, Robert Iakobashvili ([EMAIL
PROTECTED]) wrote:
> > > If I am correct, a TCP server can make up to
> > > 64K accepts for a port at a single IP-address.
> >
> > No, it is essentially unlimited - linux uses local/remote addr/port
> > tuples for hash chains, so there is no per-addr limits.
> > If there is some kind of binds, then yes, only 64k ports per address.
>
> Thanks, it clarified me the issue.
> Probably, I am experiencing some local problem with
> the web-server I am using for tests.
If your setup is :
Server A with one IP address listening to port 80
'Client B' with one IP address, trying to open many sockets to A (port 80)
Then yes you have a 64k limit for this particular client B. Just add 15 more
clients (or 16 IP addresses on B) if you really want to stress A ;)
Actually, each client has its own secondary IP, and
the problem was in nginx server configuration (errare humanum est).
Thank you, Eric.
--
Sincerely,
Robert Iakobashvili,
coroberti %x40 gmail %x2e com
...........................................................
http://curl-loader.sourceforge.net
A web testing and traffic generation tool.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
