You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the allocator has a single linked list of blocks. This is rather bad, since the two primary operations only consider a subset of those blocks:
allocation is only interested in free blocks, hence each allocated block is ignored
deallocation is only interested in used blocks, ignoring the free ones.
Therefore it makes sense to have two separate linked lists, one for free and one for used blocks. This should make maintaining the lists somewhat easier as well, as the lists have now a narrower scope. It certainly will speed up the searching for blocks, since only candidates for the operation in question are considered.
The text was updated successfully, but these errors were encountered:
Currently, the allocator has a single linked list of blocks. This is rather bad, since the two primary operations only consider a subset of those blocks:
Therefore it makes sense to have two separate linked lists, one for free and one for used blocks. This should make maintaining the lists somewhat easier as well, as the lists have now a narrower scope. It certainly will speed up the searching for blocks, since only candidates for the operation in question are considered.
The text was updated successfully, but these errors were encountered: