netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: NetDev <netdev@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>
Subject: Re: OOM when adding ipv6 route:  How to make available more per-cpu memory?
Date: Mon, 08 Nov 2010 12:02:11 +0100	[thread overview]
Message-ID: <1289214131.2820.187.camel@edumazet-laptop> (raw)
In-Reply-To: <4CD58B9C.2030006@candelatech.com>

Le samedi 06 novembre 2010 à 10:08 -0700, Ben Greear a écrit :

> At least I don't see any percpu dumps in dmesg.  I vaguely remember
> someone posting some ipv6 address scalability patches some time back.
> I think they had to hack on /proc fs as well.  I'll see if I can
> dig those up.
> 
> > Make sure udev / hotplug is not the problem, if you create your devices
> > very fast.
> 
> We can create the macvlans w/out problem, though I'm sure that could
> be sped up.  The problem is when we try to add IPv6 addresses to
> them.

I see. Did you check /proc/sys/net/ipv6/ tunables ?

For example, I bet you need to make route/max_size a bigger value than
default (4096)

Following is working for me

echo 16384 >/proc/sys/net/ipv6/route/max_size
modprobe dummy numdummies=2000
for a in `seq 1 1999`
do
 ip -6 add add 4444::444:$a/24 dev dummy$a
done

ip -6 ro | wc -l
6008




  reply	other threads:[~2010-11-08 11:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 17:19 OOM when adding ipv6 route: How to make available more per-cpu memory? Ben Greear
2010-11-05 18:06 ` Eric Dumazet
2010-11-05 18:15   ` Ben Greear
2010-11-05 20:20     ` Eric Dumazet
2010-11-05 20:26       ` Ben Greear
2010-11-05 20:53         ` Eric Dumazet
2010-11-05 22:11       ` Eric Dumazet
2010-11-06  0:07         ` Ben Greear
2010-11-06  7:26           ` Eric Dumazet
2010-11-06 17:08             ` Ben Greear
2010-11-08 11:02               ` Eric Dumazet [this message]
2010-11-08 17:45                 ` Ben Greear
2010-11-08 17:55                   ` Eric Dumazet
2010-11-08 18:08                     ` Ben Greear
2010-11-08 21:27                 ` Ben Greear
2010-11-08 21:40                   ` Eric Dumazet
2010-11-06  9:11         ` Tejun Heo

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=1289214131.2820.187.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).