Roland Mainz wrote: >>> A while aho when I was in MPK there was a discussion whether it would >>> make sense to rip-out the existing |libc::malloc()| and port the libast >>> implementation over to libc. The only problem so far was finding enougth >>> free time to do it... ;-( >> I think I'd rather see libumem replace the default allocator. > > Erm... libast's allocator and libumem have similar debugging features > while libast AFAIK avoids fragmentation better and is async-signal safe. > Maybe we should do some kind of hybrid with libast's algorithm and > libumem's debugging features...
libumem also provides the umem_cache_alloc() functionality it isn't just a DEBUG/alternate malloc/free so libast's algorithm + libumem's debug features isn't enough to replace libumem. -- Darren J Moffat
