Subject: Re: alloc.c etc.
To: new-httpd@hyperreal.com
Date: Tue, 14 Jan 1997 13:48:42 +0000 (GMT)
From: Ben Laurie <ben@gonzo.ben.algroup.co.uk>
In-Reply-To: <ML-2.3.853253645.3061.rasmus@inet-dev> from
 "rasmus@mail1.bellglobal.com" at Jan 14, 97 09:54:05 am
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID: <9701141348.aa28699@gonzo.ben.algroup.co.uk>
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

rasmus@mail1.bellglobal.com wrote:
> 
> > > There is no need for any calls to free() in the Apache pool-based memory
> > > allocation scheme.  malloc'ed memory cannot be returned to the system
> > > until after the process exits anyway.  All free() does is indicate that
> > > the memory block free'ed is available for re-use by the same process. 
> > > If you 
> > 
> > I don't think that's a particularly valid assumption since FreeBSD's
> > malloc does return memory to the system when it's freed.
> 
> That may be.  I am not familiar with FreeBSD.  Traditional Unix platforms
> are not able to give data space back to the system for use by other processes.

I don't think that's completely true. The sbrk() system will give back memory.
However, I believe it is true that most malloc() implementations never attempt
this.

Cheers,

Ben.

-- 
Ben Laurie                Phone: +44 (181) 994 6435  Email: ben@algroup.co.uk
Freelance Consultant and  Fax:   +44 (181) 994 6472
Technical Director        URL: http://www.algroup.co.uk/Apache-SSL
A.L. Digital Ltd,         Apache Group member (http://www.apache.org)
London, England.          Apache-SSL author