From owner-freebsd-current  Mon Sep 22 14:06:41 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA19995
          for current-outgoing; Mon, 22 Sep 1997 14:06:41 -0700 (PDT)
Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA19989
          for <current@freebsd.org>; Mon, 22 Sep 1997 14:06:38 -0700 (PDT)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
	by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id PAA02060;
	Mon, 22 Sep 1997 15:06:32 -0600 (MDT)
Message-Id: <199709222106.PAA02060@pluto.plutotech.com>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Nate Williams <nate@mt.sri.com>
cc: "Justin T. Gibbs" <gibbs@plutotech.com>, Bruce Evans <bde@zeta.org.au>,
        current@freebsd.org
Subject: Re: callouts in CAM (was Re: cvs commit:) 
In-reply-to: Your message of "Mon, 22 Sep 1997 14:51:25 MDT."
             <199709222051.OAA02828@rocky.mt.sri.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 22 Sep 1997 15:06:21 -0600
From: "Justin T. Gibbs" <gibbs@plutotech.com>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Fair enough.  Does the new scheme allow for dynamic allocation of
>callouts?  I noticed that was on the TODO list for the original authors.

Yes, but it's still not implemented.  I think that we should push this
onto the client instead of attempting to do some kind of low water-mark
early allocation.  In other words, allocate a fairly small initial pool
for most applications and then have systems like CAM allocate a callout
on an as-needed basis.

>Nate

--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================