Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755164Ab2EZDjr (ORCPT ); Fri, 25 May 2012 23:39:47 -0400 Received: from mail-ee0-f46.google.com ([74.125.83.46]:35437 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754459Ab2EZDjp (ORCPT ); Fri, 25 May 2012 23:39:45 -0400 Subject: Re: [PATCH] net: compute a more reasonable default ip6_rt_max_size From: Eric Dumazet To: Arun Sharma Cc: David Miller , netdev@vger.kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <4FC02777.5070003@fb.com> References: <4FC0063E.8080209@fb.com> <20120525.185131.2017517041016424794.davem@davemloft.net> <4FC01F1B.1080009@fb.com> <20120525.201150.1782581593120395710.davem@davemloft.net> <4FC02777.5070003@fb.com> Content-Type: text/plain; charset="UTF-8" Date: Sat, 26 May 2012 05:39:40 +0200 Message-ID: <1338003580.10135.6.camel@edumazet-glaptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 988 Lines: 30 On Fri, 2012-05-25 at 17:44 -0700, Arun Sharma wrote: > On 5/25/12 5:11 PM, David Miller wrote: > > >> These were not admin configured routes. They were discovered via ipv6 > >> neighbor discovery. > > > > Then such default routes should either be: > > > > 1) Passed over by GC > > > > 2) Trigger neighbour discovery when GC'd > > It's possible that there is a bug somewhere - we didn't get a chance to > dig deeper. What we observed is that as we got close to the 4096 limit, > some hosts were becoming unreachable. A modest increase in the routing > table size made things better. > > -Arun But your patch is not a "modest increase", so whats the deal ? A modest increase would be 8192 instead of 4096, regardless of RAM size. -- 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/