From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267083AbUBFAYm (ORCPT ); Thu, 5 Feb 2004 19:24:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267090AbUBFAYe (ORCPT ); Thu, 5 Feb 2004 19:24:34 -0500 Received: from fw.osdl.org ([65.172.181.6]:13505 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S267083AbUBFAWj (ORCPT ); Thu, 5 Feb 2004 19:22:39 -0500 Date: Thu, 5 Feb 2004 16:23:55 -0800 From: Andrew Morton To: "Chen, Kenneth W" Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org Subject: Re: Limit hash table size Message-Id: <20040205162355.7a4d4858.akpm@osdl.org> In-Reply-To: References: X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i586-pc-linux-gnu) 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 "Chen, Kenneth W" wrote: > > Andrew, > > Will you merge the changes in the network area first while I'm working > on the solution suggested here for inode and dentry? The 2GB tcp hash is > the biggest problem for us right now. Is there some reason why TCP could not also end up creating 100's of millions of objects?