From owner-freebsd-current Wed Sep 24 19:23:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA17117 for current-outgoing; Wed, 24 Sep 1997 19:23:04 -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 TAA17109 for ; Wed, 24 Sep 1997 19:22:57 -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 UAA05484; Wed, 24 Sep 1997 20:22:27 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id UAA16284; Wed, 24 Sep 1997 20:22:22 -0600 (MDT) Date: Wed, 24 Sep 1997 20:22:22 -0600 (MDT) Message-Id: <199709250222.UAA16284@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: <199709250017.RAA02618@usr03.primenet.com> References: <199709241523.JAA12165@rocky.mt.sri.com> <199709250017.RAA02618@usr03.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > 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. > > Which bucket is an 8 tick timeout in? It's going to be in the current > bucket or any one of the 7 following it, depending on how many sofclocks > have happenend since the queue. We're not hashing on the tick, we're hashing on the function/arguements. The result of the hash gives us a pointer to the exact element. Nate