Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!mit-eddie!uw-beaver!tektronix!sequent!mntgfx!gssc!geoffs
From: geoffs@gssc.UUCP (Geoff Shapiro)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Fragmentation on DOS - HELP !
Message-ID: <417@gssc.UUCP>
Date: Fri, 22-May-87 01:59:18 EDT
Article-I.D.: gssc.417
Posted: Fri May 22 01:59:18 1987
Date-Received: Sat, 23-May-87 18:09:12 EDT
References: <287@pyuxv.UUCP> <764@usfvax2.UUCP> <3617@gitpyr.gatech.EDU>
Reply-To: geoffs@gssc.UUCP (Geoff Shapiro)
Organization: Graphic Software Systems, Beaverton Or
Lines: 18

In article <3617@gitpyr.gatech.EDU> roy@gitpyr.gatech.EDU (Roy Mongiovi) writes:
>I sincerely hope that MSC does not use the DOS functions directly to allocate
>memory, since 16 bytes is a tremendous overhead for small blocks.  I don't
>own Microsoft C, so someone else will have to look into it.
>-- 

MSC's memory management routines do indeed call Dos to procure chunks of
memory, BUT these chunks of memory are always allocated from Dos in
minimum block sizes (you may change the minimum size, described in MSC
manual) and they are then submanaged by the runtime library's memory
management routines.

I am sure that the MSC memory management routines' header overhead for
submanaged memory blocks is a bit more concise.

Geoff Shapiro
Graphic Software Systems
(503) 641-2200