From owner-freebsd-current Wed Sep 24 08:23:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA04546 for current-outgoing; Wed, 24 Sep 1997 08:23: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 IAA04541 for ; Wed, 24 Sep 1997 08:23:31 -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 JAA00986; Wed, 24 Sep 1997 09:23:16 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA12165; Wed, 24 Sep 1997 09:23:14 -0600 (MDT) Date: Wed, 24 Sep 1997 09:23:14 -0600 (MDT) Message-Id: <199709241523.JAA12165@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), julian@whistle.com, gibbs@plutotech.com, bde@zeta.org.au, current@freebsd.org Subject: Re: new timeout routines In-Reply-To: <199709240621.XAA05226@usr07.primenet.com> References: <199709231452.IAA07122@rocky.mt.sri.com> <199709240621.XAA05226@usr07.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > These were my thoughts while reading the paper. I was a little > > > dissapointed that you didn't implement the compatible interface that > > > they originally wrote. > > > > Now, this is something I don't understand. Why the need for the > > 'cookies' in the drivers, since I don't see what it gains us? (Time to > > go re-read the code and paper again.) > > Untimeout this particular timeout without traversing the whole list > of possible timeouts. 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. Nate