malloc() and spinlocks

[David Boreham]

> HTML page in Konqueror, but I guess we can live with that. I'm not very
keen
> on the idea of the default malloc() implementation being optimalized for
the
> rare case of many threads extensively using the heap or having debug stuff
in
> it (=hooks), on the other hand having another malloc in libkdecore causes
> some trouble in special cases :(.

Hmm....I spend most of my life grumbling that code is optimized for the
rare case that the application is single threaded and the machine only has
one CPU :)

Please do not break the SMP performance of malloc (at least don't break it
more than it is already).

Thanks.