From owner-freebsd-current Wed Sep 24 09:45:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA09618 for current-outgoing; Wed, 24 Sep 1997 09:45:05 -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 JAA09612 for ; Wed, 24 Sep 1997 09:45:02 -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 KAA01542; Wed, 24 Sep 1997 10:44:18 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA12667; Wed, 24 Sep 1997 10:44:16 -0600 (MDT) Date: Wed, 24 Sep 1997 10:44:16 -0600 (MDT) Message-Id: <199709241644.KAA12667@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Justin T. Gibbs" Cc: Nate Williams , Terry Lambert , julian@whistle.com, bde@zeta.org.au, current@freebsd.org Subject: Re: new timeout routines In-Reply-To: <199709241611.KAA22907@pluto.plutotech.com> References: <199709241523.JAA12165@rocky.mt.sri.com> <199709241611.KAA22907@pluto.plutotech.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs writes: > >Build a hash list that uses the (fn, args) parameter at timeout time > >(which is what the result of the cookie is), and then get to the timeout > >via hashing back on this with untimeout(fn, args). No need for the > >drivers to hold onto the cookie, since you have all the necessary > >information. > > No-one said this wasn't possible. It just takes additional space and > makes untimeout's running time non-deterministic. I decided it was > 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? Nate