All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Gaspar Chilingarov <gasparch@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: PROBLEM: Linux kernel 2.6.31 IPv4 TCP fails to open huge amount of 	outgoing connections (unable to bind ... )
Date: Tue, 20 Apr 2010 16:07:37 -0700	[thread overview]
Message-ID: <4BCE33B9.8050101@candelatech.com> (raw)
In-Reply-To: <g2z46c8cb3e1004201517i5641a75cze2ec5bd33e81fb0f@mail.gmail.com>

On 04/20/2010 03:17 PM, Gaspar Chilingarov wrote:

> I would be grateful for hints where to look in the source -- may be I
> can produce some working patches for it.

I've opened 40,000 connections to/from my machine (over external interfaces)
on a slightly hacked .31 kernel.  This is 80,000 sockets total.  I bind
to local IP and port range, as well as SO_BINDTODEVICE.

I'm using a 64-bit system with 12GB of RAM, quad-core i7 3.3Ghz, etc.

It takes a lot of RAM to do this but you can probably use less RAM in user-space
than I am.  Be sure to set your socket buffer sizes small.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  parent reply	other threads:[~2010-04-20 23:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 22:17 PROBLEM: Linux kernel 2.6.31 IPv4 TCP fails to open huge amount of outgoing connections (unable to bind ... ) Gaspar Chilingarov
2010-04-20 22:31 ` Eric Dumazet
2010-04-20 23:18   ` Gaspar Chilingarov
2010-04-20 23:42     ` Eric Dumazet
2010-04-21  0:14       ` Evgeniy Polyakov
2010-04-20 23:07 ` Ben Greear [this message]
2010-04-20 23:20   ` Gaspar Chilingarov
2010-04-20 23:20   ` Gaspar Chilingarov
2010-04-20 23:30     ` Ben Greear
2010-04-20 23:35       ` Gaspar Chilingarov
2010-04-20 23:49         ` Ben Greear
2010-04-20 23:57           ` Gaspar Chilingarov
2010-04-21  0:14             ` Eric Dumazet
2010-04-21  0:05           ` Eric Dumazet
2010-04-21  0:12             ` Gaspar Chilingarov
2010-04-21  0:14             ` David Miller
2010-04-21  0:30             ` Evgeniy Polyakov
2010-04-21  2:04               ` David Miller
2010-04-21  5:46               ` Eric Dumazet
2010-04-21  8:25                 ` Evgeniy Polyakov
2010-04-21  9:02                   ` Eric Dumazet
2010-04-21  9:58                     ` Evgeniy Polyakov
2010-04-21 10:21                       ` Eric Dumazet
2010-04-21 11:27                       ` Eric Dumazet
2010-04-21 16:52                         ` George B.
2010-04-21 18:27                         ` Evgeniy Polyakov
2010-04-21 18:43                           ` Eric Dumazet
2010-04-21 18:58                             ` Evgeniy Polyakov
2010-04-21 19:26                               ` Eric Dumazet
2010-04-21 20:08                                 ` Evgeniy Polyakov
2010-04-23  2:06                                   ` David Miller
2010-04-25 14:26                                 ` Michael S. Tsirkin
2010-04-25 15:56                                   ` Evgeniy Polyakov
2010-04-25 16:13                                     ` Eric Dumazet
2010-04-25 16:21                                     ` Eric Dumazet
2010-04-25 16:35                                       ` Michael S. Tsirkin
2010-04-25 22:08                                         ` David Miller
2010-04-21 19:03 ` Narendra Choyal

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=4BCE33B9.8050101@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=gasparch@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.