From owner-freebsd-hackers  Sat Mar  1 22:22:57 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA24334
          for hackers-outgoing; Sat, 1 Mar 1997 22:22:57 -0800 (PST)
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24328
          for <hackers@FreeBSD.ORG>; Sat, 1 Mar 1997 22:22:42 -0800 (PST)
Received: (from imb@localhost)
          by asstdc.scgt.oz.au (8.8.5/BSD4.4) id RAA12400
          Sun, 2 Mar 1997 17:21:36 +1100 (EST)
From: michael butler <imb@scgt.oz.au>
Message-Id: <199703020621.RAA12400@asstdc.scgt.oz.au>
Subject: Re: ok, final sockhash changes, new diff
In-Reply-To: <199703020156.RAA00329@root.com> from David Greenman at "Mar 1, 97 05:56:24 pm"
To: dg@root.com
Date: Sun, 2 Mar 1997 17:21:35 +1100 (EST)
Cc: davem@jenolan.rutgers.edu, netdev@roxanne.nuclecu.unam.mx,
        hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

David Greenman writes:

>    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.

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 ? :-)

	michael