mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert Iakobashvili" <coroberti@gmail.com>
To: djones@rossove.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: Scaling Max IP address limitation
Date: Mon, 25 Jun 2007 11:47:31 +0300	[thread overview]
Message-ID: <7e63f56c0706250147w508d3aeay5f7aaca8215953c8@mail.gmail.com> (raw)
In-Reply-To: <467F063A.2030805@rossove.com>

David,

On 6/25/07, David Jones <djones@rossove.com> wrote:

> >> > I am trying to add multiple IP addresses ( v6 ) to my FC7 box on eth0.
> >> > But I am hitting a max limit of 4000 IP address . Seems like there
> >> is a
> >> > limiting variable in linux kernel (which one? ) that prevents from
> >> > adding more IP addresses than 4096. What do I need to change in Linux
> >> > kernel  ( and then recompile ) to be able to add more IP addresses
> >> than 4K addresses per system? ..
> >
> I am using the "ip add " command looping sequentially up until RTNETLINK
> starts refusing to add more IP addresses.
> How are you adding via Netlink interface ?

Yes.

OK. Now it looks that I am reproducing something.

Running curl-loader with 60K.conf (edit the name of interface) configuration:
#ulimit -n 80000
#curl-loader -f ./conf-examples/60K.conf -w
 it adds successfully 60 000 secondary IPv4 addresses as seen by
#ip addr | wc -l

When I tryed adding IPv6 addresses, using ipv6.conf with addresses
range edited:
IP_ADDR_MIN=  2001:db8:fff5:1::1
IP_ADDR_MAX= 2001:db8:fff5:ffff::1

I am getting after initial successes some errors:
"rtnl_talk(): RTNETLINK answers: Cannot allocate memory"
and
#ip addr | wc-l is 8194.

8K addresses added and no more? It might be a memory issue. Y can dig
into the code and look into the allocation process and limits on the
kernel memory for IPv6.

The physical memory on my computer is 480 MB.
kernel is vanilla 2.6.20.7.

Try to see, what happens, when you increase the memory on your comp,
if an option.

-- 
Sincerely,
Robert Iakobashvili,
coroberti %x40 gmail %x2e com
...........................................................
http://curl-loader.sourceforge.net
A web testing and traffic generation tool.

  reply	other threads:[~2007-06-25  8:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-24 17:20 David Jones
2007-06-24 18:02 ` Andrew Morton
2007-06-24 19:59   ` Robert Iakobashvili
2007-06-25  0:03     ` David Jones
2007-06-25  8:47       ` Robert Iakobashvili [this message]
2007-06-25  9:30         ` Jan Engelhardt
2007-06-25  9:41           ` Robert Iakobashvili
2007-06-25 12:38             ` Jan Engelhardt
2007-06-25 12:44               ` Robert Iakobashvili
2007-06-25 17:26                 ` David Jones
     [not found]                   ` <7e63f56c0706260756q504bc4c2sa8905fbaeed4308d@mail.gmail.com>
2007-06-26 14:58                     ` Robert Iakobashvili
2007-06-24 20:19   ` Robert Iakobashvili
2007-06-24 19:08 ` Kyle Moffett
2007-06-24 19:54   ` David Stevens
2007-06-24 19:58   ` Jan Engelhardt
2007-06-24 20:44     ` david
2007-06-24 20:52       ` Jan Engelhardt
2007-06-24 21:51     ` Kyle Moffett
2007-06-25  9:36     ` Patrick McHardy

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=7e63f56c0706250147w508d3aeay5f7aaca8215953c8@mail.gmail.com \
    --to=coroberti@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=djones@rossove.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®