From owner-freebsd-hackers Wed Jan 3 18:10:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA26966 for hackers-outgoing; Wed, 3 Jan 1996 18:10:57 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA26958 for ; Wed, 3 Jan 1996 18:10:54 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA09725; Thu, 4 Jan 1996 12:40:56 +1030 From: Michael Smith Message-Id: <199601040210.MAA09725@genesis.atrad.adelaide.edu.au> Subject: Re: X for install To: terry@lambert.org (Terry Lambert) Date: Thu, 4 Jan 1996 12:40:56 +1030 (CST) Cc: gibbs@freefall.freebsd.org, phk@critter.tfs.com, jkh@time.cdrom.com, obrien@cs.ucdavis.edu, freebsd-hackers@FreeBSD.org In-Reply-To: <199601031852.LAA15173@phaeton.artisoft.com> from "Terry Lambert" at Jan 3, 96 11:52:10 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > You need a distinction between low persistance (probe code, etc.), > medium persistance (buffer pool allocations), and high persistance > (kernel and non-transient modules) memory objects to prevent serious > fragmentation in an autoload process. Why? You load a driver, it sets up whatever it needs in terms of buffers, and then probes. If the probe succeeds, you attach it, if it fails, you throw it all out. The problem with fragmentation is in autodiscard, not autoload. > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "Who does BSD?" "We do Chucky, we do." [[