From owner-freebsd-hackers Sat Mar 1 17:56:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA13064 for hackers-outgoing; Sat, 1 Mar 1997 17:56:50 -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 RAA13059 for ; Sat, 1 Mar 1997 17:56:47 -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 UAA10352; Sat, 1 Mar 1997 20:56:33 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id UAA09551; Sat, 1 Mar 1997 20:56:20 -0500 Date: Sat, 1 Mar 1997 20:56:20 -0500 Message-Id: <199703020156.UAA09551@jenolan.caipgeneral> From: "David S. Miller" To: dg@root.com CC: netdev@roxanne.nuclecu.unam.mx, hackers@FreeBSD.ORG In-reply-to: <199703020156.RAA00329@root.com> (message from David Greenman on Sat, 01 Mar 1997 17:56:24 -0800) Subject: Re: ok, final sockhash changes, new diff Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: David Greenman Date: Sat, 01 Mar 1997 17:56:24 -0800 The reason just occured to me: In the case of a server with googols of IP aliases, the {faddr, lport, fport} are all the same (faddr and fport are wildcards) for the listening sockets of a given service (say http)...so the only thing unique is the laddr, which if not included in the hash, will cause all of the listening sockets to be hashed to the same bucket. Jinx, you'll see that I just made a posting stating this as well ;) ---------------------------------------------//// 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 /_____________/ / // /_/ ><