@RichFelker Offering precise first-best-fit like jemalloc also goes a long way towards reducing fragmentation but O(log n) instead of O(1).
@CopperheadSec There's no sense in optimizing for speed of allocations larger than small_const*memset_rate*malloc_time.
-
-
@CopperheadSec This is because you can assume any reasonable caller actually _uses_ the amount of mem it allocs, and use takes > memset_time -
@CopperheadSec This is why I have no interest in avoiding mmap for lg (>128k) allocs - memset(128k) is much slower than mmap. -
@RichFelker Using mmap, mprotect and munmap grabs the global mmap_sem writer lock though, and that hurts. Even madvise calls get blocked. -
@RichFelker It's not particularly slow in one thread, but it doesn't scale. You could argue that it's the kernel's problem to address. -
@RichFelker The region-based design works well with small regions too but even 32k regions are wiping out 3 bits of ASLR entropy. Not ideal.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.