Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757595Ab1BPB3l (ORCPT ); Tue, 15 Feb 2011 20:29:41 -0500 Received: from ns3.baby-dragons.com ([64.62.236.141]:50136 "EHLO ns3.baby-dragons.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757273Ab1BPB3c (ORCPT ); Tue, 15 Feb 2011 20:29:32 -0500 Date: Tue, 15 Feb 2011 16:29:20 -0900 (AKST) From: "Mr. James W. Laferriere" To: Lukasz Trabinski cc: Linux Kernel Maillist , NetDev Subject: Re: [kernel] net.ipv6.route.max_size In-Reply-To: Message-ID: References: User-Agent: Alpine 2.01 (LNX 1184 2008-12-16) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (ns3.baby-dragons.com [64.62.236.141]); Wed, 16 Feb 2011 01:29:26 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2609 Lines: 67 Hello Lukasz , Since I have not seen anyone else suggest this or to do so I'll forward this onto the NetDev list for their perusal as well . Hth , JimL On Mon, 14 Feb 2011, Lukasz Trabinski wrote: > 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-14 20:26:12.000000000 +0100 > +++ route.c 2011-02-14 20:30:04.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; > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | babydr@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/