All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Trabinski <lukasz@trabinski.net>
To: netdev@vger.kernel.org
Subject: net.ipv6.route.max_size
Date: Mon, 14 Feb 2011 21:39:55 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1102142136520.10107@oceanic.wsisiz.edu.pl> (raw)

Hello

IPv6 route table size is still growing. In stanard linux box configuration
with IPv6 BGP session (with ipv6 world table) and BGP application like Quagga,
we have problem like this:

2011/02/12 18:43:52 ZEBRA: netlink-cmd error: Cannot allocate memory,
type=RTM_NEWROUTE(24), seq=11124600, pid=0

This problem shows us that's all prefixes comes from BGP can't be install into 
FIB

IN BGP application we can see, that's we recive 4484 prefixes from ipv6 
neighbor:

cosmos> show bgp summary
Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down State/PfxRcd
2001:1a68:0:c::1
                 4 24724  431945   70172        0    0    0 2d01h18m     4484


I suggest that net->ipv6.sysctl.ip6_rt_max_size should be increase.
Below _simple_ patch for this problem. I don't understand why in ipv4/route we 
have different method to count ip4_rt_max_size? My value 65536 in near future 
will be also wrong. I know also, that we can change it by sysctl, but I thing 
that it's not good way to fix it.


--- route.c~    2011-02-08 01:03:55.000000000 +0100
+++ route.c     2011-02-14 20:48:53.000000000 +0100
@@ -2708,7 +2708,7 @@
  #endif

         net->ipv6.sysctl.flush_delay = 0;
-       net->ipv6.sysctl.ip6_rt_max_size = 4096;
+       net->ipv6.sysctl.ip6_rt_max_size = 65536;
         net->ipv6.sysctl.ip6_rt_gc_min_interval = HZ / 2;
         net->ipv6.sysctl.ip6_rt_gc_timeout = 60*HZ;
         net->ipv6.sysctl.ip6_rt_gc_interval = 30*HZ;


             reply	other threads:[~2011-02-14 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 20:39 Lukasz Trabinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-14 20:03 net.ipv6.route.max_size Lukasz Trabinski

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=alpine.LFD.2.00.1102142136520.10107@oceanic.wsisiz.edu.pl \
    --to=lukasz@trabinski.net \
    --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 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.