From owner-freebsd-hackers  Tue Jul  4 05:14:59 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id FAA23577
          for hackers-outgoing; Tue, 4 Jul 1995 05:14:59 -0700
Received: from saul1.u.washington.edu (spaz@saul1.u.washington.edu [140.142.82.10])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA23571
          for <FreeBSD-hackers@freefall.cdrom.com>; Tue, 4 Jul 1995 05:14:58 -0700
Received: by saul1.u.washington.edu
	(5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA06981;
	Tue, 4 Jul 95 05:14:58 -0700
X-Sender: spaz@saul1.u.washington.edu
Date: Tue, 4 Jul 1995 05:14:55 -0700 (PDT)
From: John Utz <spaz@u.washington.edu>
To: FreeBSD hackerlist <FreeBSD-hackers@freefall.cdrom.com>
Subject: dlmalloc
Message-Id: <Pine.OSF.3.91j.950704051121.9067B-100000@saul1.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

I recall reading a report on this list of someone using dlmalloc ( doug 
lea malloc? ) with good success.

	has anyone else made use of it and gotten any results that they 
think are worthy of mention? it seems like a reasonable alternetive for 
the ram limited.....

*******************************************************************************
 John Utz	spaz@stein.u.washington.edu
	idiocy is the impulse function in the convolution of life