On Sat Feb 4 17:25:37 2023 +0000, Rémi Bernon wrote:
Yes, although it's not strictly synchronized with the block allocation: the block allocation may complete using the last block of the group, but then when we try to set the `GROUP_FLAG_FREE` flag, we find that another thread has freed a block. In which case the flag isn't set of course. It is also possible to think about it being equivalent to *the group is not linked anymore and the last thread to release a block to it gets ownership and is responsible of either putting the group back into a free list, or release it*.
Thanks for your remark! Is there a reason that we do not _immediately_ put the group back to the group list after a block has been freed and the group now has block slots available?