Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!linus!philabs!prls!amdimage!amdcad!amd!vecpyr!lll-crg!gymble!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.lang.c
Subject: Re: malloc(), virtual memory
Message-ID: <1548@umcp-cs.UUCP>
Date: Wed, 11-Sep-85 11:35:03 EDT
Article-I.D.: umcp-cs.1548
Posted: Wed Sep 11 11:35:03 1985
Date-Received: Sat, 14-Sep-85 01:47:39 EDT
References: <1285@brl-tgr.ARPA> <1506@umcp-cs.UUCP> <5079@allegra.UUCP>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 24

> ...  Another ``gotcha'' to beware of is that space, once allocated,
> is never broken into smaller pieces. [...] Dunno if this is fixed
> under 4.3.
>
> John P. Linderman  Space Cadet  allegra!jpl

I doubt it will be; it has not yet been done.  It might create yet
another ``gotcha'', however, as coalescing smaller blocks is fairly
tricky.

By the way, I quote from my own version of the CalTech malloc which
I use in my Emacs:

 /* If there are no blocks of the appropriate size, go get some */
 /* COULD SPLIT UP A LARGER BLOCK HERE ... ACT */
    if (nextf[nunits] == NULL)
	morecore (nunits);

I put that comment in when I rewrote most of the code; the RCS logs
say that was 84/06/29---more than a year ago.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland