3 ms·
In such extreme cases you can (and should) use your own allocation strategy.
by ChrisSD 8y ago
In such extreme cases you can (and should) use your own allocation strategy.
- vardump 8y agoYeah, but I'm not entirely clear how I'd for example get std::vector to use a mmap'ed range, that I could zero-copy grow. Also in that case I might want to grow it by a fixed amount, once it grows past a certain threshold. It's a shame one needs to write another vector implementation just for that.
- ChrisSD 8y agoWhy wouldn't writing an allocator class be enough for mmap?
- BeeOnRope 8y agoProbably not, because the allocators don't expose the "extend" or "realloc" concept, so all you'll see from within your allocator is a request for an entire new region that vector wants in order to copy the new stuff into. To implement a growing allocation , you'll have to create a custom vector, pretty much.
- Timmah 8y agoHow would you ensure nothing was used in the region after the original allocation?