From owner-freebsd-questions Wed Mar 6 17:08:27 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA19032 for questions-outgoing; Wed, 6 Mar 1996 17:08:27 -0800 (PST) Received: from tulpi.interconnect.com.au (root@tulpi.interconnect.com.au [192.189.54.18]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA19017 for ; Wed, 6 Mar 1996 17:08:24 -0800 (PST) Received: (from ahill@localhost) by tulpi.interconnect.com.au id MAA10168 (8.6.11/IDA-1.6); Thu, 7 Mar 1996 12:08:10 +1100 Date: Thu, 7 Mar 1996 12:08:05 +1100 (EST) From: Anthony Hill To: Michael Smith cc: luigi@labinfo.iet.unipi.it, msmith@atrad.adelaide.edu.au, questions@freebsd.org Subject: Re: Before and after the cure (was Re: malloc upgrade) In-Reply-To: <199603070047.LAA27575@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk On Thu, 7 Mar 1996, Michael Smith wrote: > The XFree people are working on a custom allocator specifically tuned to > the way that X uses memory. You can build the XFree servers using the > stock malloc (the current distributions), with gnumalloc (which is better) > or with phkmalloc (the 'new' malloc Luigi is talking about). Unfortunatly, being fairly new to this stuff, I dont know how to go about building XFree using a different malloc. It seems as though lots of people know how to fix this really annoying 'feature', so I keep expecting that someone will produce a patch or XFree port which includes an X aware malloc. > Either of the latter two will improve the server's behaviour. I would > expect the up-and-coming custom allocator to be significantly better again. This indeed sounds like something to look forward to. Anthony