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 18:55:12 +0100 [thread overview]
Message-ID: <1289238912.3167.4.camel@edumazet-laptop> (raw)
In-Reply-To: <4CD83752.1070501@candelatech.com>
Le lundi 08 novembre 2010 à 09:45 -0800, Ben Greear a écrit :
> That helps. I'm getting all of the IP addrs set now, but
> having trouble with some of the default gateways (I have one
> routing table per interface).
>
> ./local/sbin/ip -6 route replace default via 2002:9:8::1 dev eth7#458 table 726
> RTNETLINK answers: No buffer space available
>
> dmesg is full of this:
>
> [247106.294743] ipv6: Neighbour table overflow.
>
>
> A quick look in /proc didn't show a tunable for this, but I'll
> go grub through the code.
>
> As for the route/max_size, it would be nice to see some useful kernel
> message in dmesg when this hit. Just telling the user '-ENOMEM'
> is not at all sufficient to help them figure out the problem.
Sure, patches are welcomed. Apparently nobody yet used ipv6 with so many
devices / routes, and this nobody contributed to extend limits.
>
> For that matter, why is there such a limit anyway? IPv4 doesn't appear
> to have any such limit?
There are limits for ipv4, much bigger, you probably never noticed.
/proc/sys/net/ipv4/route/gc_elasticity:8
/proc/sys/net/ipv4/route/gc_interval:60
/proc/sys/net/ipv4/route/gc_min_interval:0
/proc/sys/net/ipv4/route/gc_min_interval_ms:500
/proc/sys/net/ipv4/route/gc_thresh:131072
/proc/sys/net/ipv4/route/gc_timeout:300
/proc/sys/net/ipv4/route/max_size:2097152 <<< HERE
/proc/sys/net/ipv4/route/min_adv_mss:256
/proc/sys/net/ipv4/route/min_pmtu:552
/proc/sys/net/ipv4/route/mtu_expires:600
/proc/sys/net/ipv4/route/redirect_load:2
/proc/sys/net/ipv4/route/redirect_number:9
/proc/sys/net/ipv4/route/redirect_silence:2048
I suggest followup discussion can got to netdev only, now per-cpu it not
anymore the problem ?
next prev parent reply other threads:[~2010-11-08 17:55 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
2010-11-08 17:45 ` Ben Greear
2010-11-08 17:55 ` Eric Dumazet [this message]
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=1289238912.3167.4.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).