3 ms·
Those aren't arenas. I'm inclined to agree with Wikipedia's definition, which does emphasise deallocation all at once: > A region, also called a zone, arena, a
by MaxBarraclough 7y ago
Those aren't arenas. I'm inclined to agree with Wikipedia's definition, which does emphasise deallocation all at once:
> A region, also called a zone, arena, area, or memory context, is a collection of allocated objects that can be efficiently deallocated all at once.
- monocasa 7y agoI mean, wiki uses zone and region here as synonyms, so according to wiki that definition applies just as much. And yet: https://www.kernel.org/doc/gorman/html/understand/understand005.html https://www.kernel.org/doc/gorman/html/understand/understand... Like, as a embedded developer, these concepts are used pretty much every day. And in a good chunk of those, deallocation isn't allowed at all, so you can't say that the definition is around deallocation at once. You can also see how glibc's malloc internally creates arenas, but that's not to deallocate at once, but instead to manage different locking semantics. https://sourceware.org/glibc/wiki/MallocInternals https://sourceware.org/glibc/wiki/MallocInternals
- Someone 7y agocan be efficiently deallocated all at once. There are implementations of arenas that, basically, act as separate memory managers. You can allocate and free memory inside them at will, but can also deallocate the whole thing in one sweep. The latter can be a lot faster, but of course, it requires you to know you can throw away all that memory in one go (handling web requests is the exemplar use case)