diff options
| -rw-r--r-- | notes/260826-use-alloc.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/notes/260826-use-alloc.md b/notes/260826-use-alloc.md index e72b006..20d53c7 100644 --- a/notes/260826-use-alloc.md +++ b/notes/260826-use-alloc.md @@ -109,6 +109,15 @@ alignment padding, but that'll be relatively small as well if you do the calculations, I'm pretty sure. In any case, no worse than other general-purpose allocators, I'm pretty sure. +*Update:* Just realized that for SIMD related reasons, it would be +best to force 16-byte alignment much earlier, and probably 32-byte +too. Also, the 64-byte alignment doesn't add any value since the +maximum object size dominates the maximum bit count for bitmaps; +therefore, the alignment values should simply go: 8, 16, 32, ... +without any alignment higher than 32. This has practically no +relevance to the strategies in the rest of this article; higher +alignments don't prevent any of the discussed designs. + ## Occupancy bitmaps |