Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

[flagged]


Your comment reads as if you believe that simply writing the syscall C wrapper yourself would constitute a meaningful enhancement to the code. We can all apply more effort to be insightful.

It’s a ‘minimal’ allocator. Reading the blog it seems to be going in depth into allocator principles, in practice, things like coalescing blocks.

I haven’t read in full so not sure if it discusses using blocks vs other structures (eg stack-based allocators, stack being the data structure not the program stack.) Ie, it’s a set of implementation choices. It still seems to reflect common ways of allocating in far more detail than many blogs I’ve read on the topic do.


How so? All production memory allocators use mmap nowadays. That's as native as it gets outside of the kernel. What were you expecting?

Who allocates the allocator?



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: