Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261873AbTEQV5d (ORCPT ); Sat, 17 May 2003 17:57:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261874AbTEQV5d (ORCPT ); Sat, 17 May 2003 17:57:33 -0400 Received: from pizda.ninka.net ([216.101.162.242]:43447 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id S261873AbTEQV5b (ORCPT ); Sat, 17 May 2003 17:57:31 -0400 Date: Sat, 17 May 2003 15:09:33 -0700 (PDT) Message-Id: <20030517.150933.74723581.davem@redhat.com> To: fw@deneb.enyo.de Cc: sim@netnation.org, linux-kernel@vger.kernel.org Subject: Re: Route cache performance under stress From: "David S. Miller" In-Reply-To: <87d6iit4g7.fsf@deneb.enyo.de> References: <20030516222436.GA6620@netnation.com> <1053138910.7308.3.camel@rth.ninka.net> <87d6iit4g7.fsf@deneb.enyo.de> X-FalunGong: Information control. X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 554 Lines: 14 From: Florian Weimer Date: Sat, 17 May 2003 09:31:04 +0200 The hash collision problem appears to be resolved, but not the more general performance issues. Or are there any kernels without a routing cache? I think your criticism of the routing cache is not well founded. - 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/