TLSFMem O(1) Memory Allocator V1.4

[platon42]

TLSFMem, the constant time memory allocator has been updated. The new version fixes several bugs and increases compatibility.  It also comes with enhanced documentation and an FAQ.

Get it here: TLSFMem V1.4

Best regards

Chris Hodges

[JosephC]

HIP HIP HOORAY!!!!!!!!  :-)

[keropi]

I read that this does not work with WarpOS, does that mean it is inactive with WOS apps, or it will cause probs with WOS apps? is it safe to use on a ppc amiga?  :-?

[platon42]

RTFM.

[keropi]

I "RTFM" as you suggest, before I posted the Q, you say:

Q: Does it run on WarpOS / PowerUP?
A: The last version V1.3 didn't due to a bug in AllocAbs. The new one
   should run under PowerUP, because according to Laire, PowerUP calls the
   exec functions. I suspect WarpOS still not to work because it's said to
   have its own PPC native implementation of the exec memory functions,
   which will cause WarpOS to run out of memory. This is due to TLSFMem
   allocating its memory from the normal memory lists and pouring each into
   TLSF mem headers, which would appear empty to the standard exec
   routines.

it might be clear to you , but I cannot understand for sure if this works or no. A "yes" or "no" is even a smaller word, you could just write that and save some time  :lol:
my main concern is if it cause any WOS errors/instabillity.

[platon42]

> I suspect WarpOS still not to work because it's said to
> have its own PPC native implementation of the exec memory functions,
> which will cause WarpOS to run out of memory.

Is pretty clear, isn't it? So I guess: No, it doesn't work with WarpOS. But I didn't try.

[keropi]

thanks...
do you think you might solve this problem in future versions?  :-)

[nOw2]

Thank you! This version works on my A4000 and with no side effects.

It'll be interesting to see how the performance holds up when it gets beyond a month's uptime, which previously bogged it down enough to need a reboot.

[JosephC]

Please consider writing a TLSFmuGuardianAngel or at least a TLSFmungWall so that we can run your incredibly excellent patch 24 hours a day, 365 days a year.

[MarkTime]

This question is not directed at Chris, but rather someone who might answer the question.

But why would Amiga need a constant time memory allocator?   Amiga is not an RTOS...   I guess, the side effect here, is not so much that its a constant time allocator, but that it tends to work better in some other fashion...i.e. the old allocator became fragmented to the point of being unusable?

While I appreciate a one-off patch aimed at fixing one of the deficencies in Amiga OS...this sort of thing, shows how not having a real Amiga, Inc. really hurts this community...such patches need to be part of OS releases.

Sadly, I understand OS releases aren't to be had anymore :-(

[JosephC]

But why would Amiga need a constant time memory allocator?

Because the allocator in OS3.9 sucks.  It gets slower and slower and slower as time goes on.  Especially when running MUI software.

You can also read the previous news announcement which has more detailed info and real life examples.