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: Tue, 26 Jun 2007 16:58:15 +0200 [thread overview]
Message-ID: <7e63f56c0706260758y728ef242o2262d2c1a0c97181@mail.gmail.com> (raw)
In-Reply-To: <7e63f56c0706260756q504bc4c2sa8905fbaeed4308d@mail.gmail.com>
Hi David,
On 6/25/07, David Jones <djones@rossove.com> wrote:
> Ok I have tried it on a Pentium-M ( 32 Bit ,) with 512 MB RAM and Core
> 2 Duo with 1Gig RAM ( running SMP kernel , 2 CPUS) with same results.
> Cant go more than ~4K addresses. I have tried them with vanilla and
> custom kernels all 2.6.19+ versions. Results are same on both systems ,
> so thats the reason I am thinking that there is some limit in kernel
>
> >> On Jun 25 2007 12:41, Robert Iakobashvili wrote:
> >> >> > I am getting after initial successes some errors:
> >> >> > "rtnl_talk(): RTNETLINK answers: Cannot allocate memory"
> >> >> > and
> >> >> > #ip addr | wc-l is 8194.
>
Looking into 2.6.20 sources:
IPv6 addresses are added via rtnetlink by:
inet6_rtm_newaddr ()
inet6_addr_add ()
ipv6_add_addr (),
where inet6_ifaddr structure is allocated by kzalloc ()
IPv4 addresses are added via rtnetlink by:
inet_rtm_newaddr () with further __inet_insert_ifa ()
inet_rtm_newaddr () allocates in_ifaddr structure by kzalloc ()
Structure inet6_ifaddr is ~85-95 bytes (depending on config options,
arch, etc),
structure in_ifaddr is ~55-60 bytes (also depending). It looks like
the case, when
size does matter.
:)
When adding secondary IPv4 addresses from /proc/slabinfo is seen, that
slab "size-64" is used, whereas for IPv6 addresses "size-128" is in use.
There should be a way to make some fine tuning and, most probably, memory
allocation for the right pool (in your case "size-128").
I do recall some echo to /proc/slabinfo, but there were some evil details.
Probably, some great people of the netdev list can advise you, how to
increase memory resources in the right direction.
Hopefully it explains the facts and directs you.
Take care,
Sincerely,
Robert Iakobashvili,
coroberti %x40 gmail %x2e com
...........................................................
http://curl-loader.sourceforge.net
A web testing and traffic generation tool.
next prev parent reply other threads:[~2007-06-26 14:58 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
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 [this message]
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=7e63f56c0706260758y728ef242o2262d2c1a0c97181@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®