Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!hsdndev!cmcl2!acf5!sabbagh
From: sabbagh@acf5.NYU.EDU (sabbagh)
Newsgroups: comp.lang.c++
Subject: Re: fragmentation of free store
Keywords: free store, new, delete
Message-ID: <1575@acf5.NYU.EDU>
Date: 4 Apr 91 21:53:07 GMT
References: <285@paradim.UUCP> <1986@godzilla.tcs.com>
Organization: New York University
Lines: 20

>     Therefore, while overloading new and delete to coalesce freed bits of
>memory will help, to really solve the problem, you need to fix the problem
>in the kernel as well (unless your application is clearly *the* primary,
>almost sole, program to be run on the machine).

Not necessarily. One could malloc a HUGE chunk of memory, then devise a memory
allocation scheme using handles (double indirection). This is how memory on
the Mac works. Using proper encapsulation, one can reduce the overhead and
make it almost completely transparent to the user.

Hadil G. Sabbagh
E-mail:		sabbagh@cs.nyu.edu
Voice:		(212) 998-3125
Snail:		Courant Institute of Math. Sci.
		251 Mercer St.
		New York,NY 10012

"Injustice anywhere is a threat to justice everywhere."
					- Martin Luther King, Jr.
Disclaimer: This is not a disclaimer.