From owner-freebsd-hackers Mon Mar 18 13:40:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA22539 for hackers-outgoing; Mon, 18 Mar 1996 13:40:10 -0800 (PST) Received: from main.gbdata.com (tty24.com3.houston.net [198.65.148.153]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA22479 for ; Mon, 18 Mar 1996 13:40:05 -0800 (PST) Received: (from gclarkii@localhost) by main.gbdata.com (8.6.12/8.6.9) id PAA06880; Mon, 18 Mar 1996 15:35:34 -0600 From: Gary Clark II Message-Id: <199603182135.PAA06880@main.gbdata.com> Subject: Re: CFV: adding phk_malloc to -stable To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Mon, 18 Mar 1996 15:35:34 -0600 (CST) Cc: luigi@labinfo.iet.unipi.it, rkw@dataplex.net, stesin@elvisti.kiev.ua, hackers@FreeBSD.ORG In-Reply-To: <7645.827142776@critter.tfs.com> from "Poul-Henning Kamp" at Mar 18, 96 09:52:56 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp wrote: > > > The issue is still up in the air, and for it to be decided we need some, > actually: a lot, of reports saying: I'm running phkmalloc in -stable and > it works fine. > > So here is again the recipe: > 1. get src/lib/libc/stdlib/malloc.[3c] from -current and stick it > into your -stable source tree. > 2. make world. > 3. beat on it A LOT > 4. report result. > I've got stable on at least 4 customer machines with the phk-malloc. They all run fine and fast. As for beating on, my home machine only has 8 megs, runs X 24 hours a day (Due to the sparc monitor on it) and has been running stable for at least a month. My poor machine thrashs at the drop of a hat or even a glance:) > In particular I'd like reports from people running NIS/YP. Not here.. sorry > > -- > Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. Gary -- Gary Clark II (N5VMF) gclarkii@FreeBSD.ORG gclarkii@GBData.COM