From: Ben Greear <greearb@candelatech.com>
To: Eric Dumazet <eric.dumazet@gmail.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: Sat, 06 Nov 2010 10:08:44 -0700 [thread overview]
Message-ID: <4CD58B9C.2030006@candelatech.com> (raw)
In-Reply-To: <1289028392.2665.2418.camel@edumazet-laptop>
On 11/06/2010 12:26 AM, Eric Dumazet wrote:
> Le vendredi 05 novembre 2010 à 17:07 -0700, Ben Greear a écrit :
>
>> We just tried creating 1000 macvlans with IPv6 addrs on a 64-bit machine
>> with 12GB RAM. Only around 520 interfaces properly set their IPs, and
>> again there are errors about of-of-memory from 'ip', but no obvious
>> splats in dmesg.
>>
>> 'top' shows 10G or so free.
>>
>> It will take some time to figure out what exactly is returning
>> the ENOMEM....
>
> At least, nothing to do with percpu stuff ?
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.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-11-06 17:08 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 [this message]
2010-11-08 11:02 ` Eric Dumazet
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=4CD58B9C.2030006@candelatech.com \
--to=greearb@candelatech.com \
--cc=eric.dumazet@gmail.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 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.