From owner-freebsd-current Wed Sep 24 10:11:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA11175 for current-outgoing; Wed, 24 Sep 1997 10:11:35 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA11167 for ; Wed, 24 Sep 1997 10:11:32 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id LAA01731; Wed, 24 Sep 1997 11:11:19 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA12805; Wed, 24 Sep 1997 11:11:18 -0600 (MDT) Date: Wed, 24 Sep 1997 11:11:18 -0600 (MDT) Message-Id: <199709241711.LAA12805@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bruce Evans Cc: gibbs@plutotech.com, nate@mt.sri.com, current@freebsd.org Subject: Re: new timeout routines In-Reply-To: <199709241700.DAA04019@godzilla.zeta.org.au> References: <199709241700.DAA04019@godzilla.zeta.org.au> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> an unacceptable tradeoff. > > > >How do you figure? untimeout is now the same as it was before, or > >aren't the cookies based on a hash table? > > Hash lookup is non-deterministic, since searching is required to handlle > collisions. You had stated earlier that it would be easy to build a perfect hash generator. It would seem to me that using either solution is still fairly predictable 'on average'. > handlers where we would prefer deterministic behaviour. Note that hash > lookup is not required for timeout() since we don't care about duplicates. Right, but hash insertion in the case of duplicates is still non-deterministic. Nate