From 7e14a912672a47fae3b306832483308efd303645 Mon Sep 17 00:00:00 2001 From: Taylan Kammer Date: Wed, 26 Aug 2026 22:52:46 +0200 Subject: Grammar/typo fix. --- notes/260826-use-alloc.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'notes') diff --git a/notes/260826-use-alloc.md b/notes/260826-use-alloc.md index 0fc2b29..8d876b1 100644 --- a/notes/260826-use-alloc.md +++ b/notes/260826-use-alloc.md @@ -135,8 +135,8 @@ Allocating a new slot should of course not require scanning possibly huge numbers of bitmaps from start to end. We keep track of the last acquired Block, and try to fit the next allocation, acquiring a new Block if it doesn't fit. Given that objects can only occupy up to -1/16 of a Block, this means we waste at most that about that much -space at the end of a Block due to the next object not fitting. +1/16 of a Block, this means we waste at most about that much space +trailing the end of a Block, when the next object doesn't fit. (The maximum waste is *just under* 1/16, because if exactly 15/16 of the block is full then another 1/16 sized object fits perfectly, but -- cgit v1.2.3