> From: Bill Stoddard [mailto:[EMAIL PROTECTED]]
> Sent: 10 September 2002 22:23

>> [Moving to [EMAIL PROTECTED]]

[...]
>> I think max_index is misunderstood.  allocator->max_index is the index of
>> the biggest block available.  index = block_size / boundary_size - 1, where
>> boundary_size is 4096.  Keeping track of max_index prevents us from scanning
>> the entire array of free lists (of different block sizes).
> 
> Code comment pretty please? I spent a very small bit of time in the
> allocator code a few months back and gave up :-)

Point taken.  Will do.

Sander

Reply via email to