Date: Fri, 16 Mar 2001 20:07:15 -0500
Message-Id: <200103170107.UAA09188@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <3ab2b577.347408@news.redshift.com> (damon@WRONG.redshift.com)
Subject: Re: DJGPP memory allocation algorithm?
References:  <3ab2b577 DOT 347408 AT news DOT redshift DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Before I go into the specifics of what the error is, can I ask the
> DJGPP gurus if there's an internal limitation on the _number_ of
> allocations one can do?

Nope.  It's limited by available virtual memory and the efficiency of
the allocator (it rounds up allocation sizes)

> I'm allocating about 50 bytes 17,000-odd times over.  Would this
> cause a problem in the allocation code?

Should be efficient; round up to 64 byte chunks = about a megabyte.