From owner-freebsd-hackers Sat Mar 1 22:28:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA24567 for hackers-outgoing; Sat, 1 Mar 1997 22:28:18 -0800 (PST) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.37.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24533 for ; Sat, 1 Mar 1997 22:28:06 -0800 (PST) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id BAA17101; Sun, 2 Mar 1997 01:27:59 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id BAA09925; Sun, 2 Mar 1997 01:27:46 -0500 Date: Sun, 2 Mar 1997 01:27:46 -0500 Message-Id: <199703020627.BAA09925@jenolan.caipgeneral> From: "David S. Miller" To: imb@scgt.oz.au CC: dg@root.com, netdev@roxanne.nuclecu.unam.mx, hackers@FreeBSD.ORG In-reply-to: <199703020621.RAA12400@asstdc.scgt.oz.au> (message from michael butler on Sun, 2 Mar 1997 17:21:35 +1100 (EST)) Subject: Re: ok, final sockhash changes, new diff Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: michael butler Date: Sun, 2 Mar 1997 17:21:35 +1100 (EST) This being the case, a simple counter (number of listens performed) added to the hash would help redistribute across buckets - don't care about wrap-around .. or am I off the planet ? :-) Huh? The placement within the tables is a product of the hash, and thus the length of the chains is as well. No counter can help change this situation. The only solution is to hash in the local IP address contained in the socket's identity. ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><