Re: Memory allocators

[Christian Reiniger <warewolf@mayn.de>]

Bjarke Hammersholt Roune wrote:

>I've finished those memory allocators I talked about. I'm not sending the
>source yet, as though I'm pretty sure there are no bugs, memory allocators
>are a little tricky to debug. I should get it done today, though.

[...]

Sounds cool. The benchmark results are also very nice (I just don't
understand the small difference between blocksizes of 16 and 128). And most
important this stuff cuts down on memory fragmentation. good.


The bad news is that I don't have too much time right now and so it's
likely to take some time until they really make it into the code. Perhaps
it's better to add them *after* the rewrite of the URL processing code and
the dir management stuff, perhaps it's better to add them *while* rewriting
these things. I'll start coding tonight, so we'll see.
In any case, adding the stuff should mainly be a metter of replacing "new"
calls with calls to the custom allocator, right?
(BTW - how do you handle out-of-memory situations?)


	Christian
--

Drive A: not responding...Formatting C: instead