> Also, syscalls in every constructor/destructor call? No thanks.
You can batch up operations just like with normal list and malloc/free. Instead of 1 page, allocate some bigger size in one go.
You can batch up operations just like with normal list and malloc/free. Instead of 1 page, allocate some bigger size in one go.
What you describe might make sense for some special cases, but adopting it as a default strategy is a bad idea IMO. (Edit: re-read your other post in this thread and realized that you are not really advocating this. Well then my reply goes mostly to nkurz :))
> even within one application, you may want to mix the storage strategies between different objects.
That's precisely what modern malloc implementations do.