implement alternate allocators
Today we provide only the incremental allocator (last_allocated_address++). It is trivial but obviously leads to contention in a multi-thread allocation. I propose two other allocators:
- hash based allocation (e.g. hash the client MAC address): it is stable (same client will likely get the same address) and predictable
- pure random: very secure, not stable nor predictable (with a real (vs fake) PRNG).
I am adding multi-threading label but it is only related.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information