Memory – Part 4: Intersec’s custom allocators

Re:Memory – Part 4: Intersec’s custom allocators by fruneau on Tuesday October 01, 2013 @07:16AM (#6475377)

Wording issue fixed.

[ Parent | on HN ]

Re:Memory – Part 4: Intersec’s custom allocators by dman on Tuesday October 01, 2013 @08:03AM (#6475547)

Is the source for the allocators freely available? Would love to study those.

[ Parent | on HN ]

Re:Memory – Part 4: Intersec’s custom allocators by fruneau on Tuesday October 01, 2013 @08:20AM (#6475619)

Unfortunately, not for the moment.

[ Parent | on HN ]

Re:Memory – Part 4: Intersec’s custom allocators by aktau on Tuesday October 01, 2013 @09:13AM (#6475847)

I'd also like to put in a request for either open-sourcing or a more detailed overview of the implementations, they sound really interesting.

[ Parent | on HN ]

Re:Memory – Part 4: Intersec’s custom allocators by fruneau on Tuesday October 01, 2013 @10:16AM (#6476271)

I'll consider writing a more detailed article on the subject. Open-sourcing the code will not be possible in the short-term.

[ Parent | on HN ]

Re:Memory – Part 4: Intersec’s custom allocators by robjh on Tuesday October 01, 2013 @10:34AM (#6476419)

In lieu of the implementation, I'd like to know if these allocators are themselves based on malloc or if you have some tricky assembly/kernel code going on somewhere.

[ Parent | on HN ]

Re:Memory – Part 4: Intersec’s custom allocators by fruneau on Tuesday October 01, 2013 @10:43AM (#6476484)

These allocators are based on mmap to build the arenas.

[ Parent | on HN ]

Re:Memory – Part 4: Intersec’s custom allocators by deletes on Tuesday October 01, 2013 @09:49AM (#6476078)

+1, for request of implementation details. I'm really curious about this.

[ Parent | on HN ]