Hi...
Maybe your explanation is reasonable. But I still can not understand why it put the last free object forward as the first and the current released object as the second? Is it redundant?
Oh no, that's not what I meant. Current released object number is assigned to the slab's free descriptor. This way, anytime somebody wants to allocate new object, this object will be used again.
While in the current freed object descriptor itself, it is assigned the number of second-to-current freed object. Using this trick, slab manager can reveal what's the next free object slot.
I hope I clarify the issue better. regards, Mulyadi -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
