On Mon, 2010-03-29 at 17:03 -0700, Yinghai Lu wrote: > > in short: It could make us to avoid use the range that we are going to > reserve, > when we try to get new position new lmb.reserved.region. I'm not too sure I follow you. For the resizing, I would just basically call a low level variant of alloc (__lmb_alloc ?) that explicitely doesn't honor the total-2 "reserved" entries in the array. Ie. It should all be one single find/allocation function. In fact, you want to split lmb_find from lmb_reserve, then just make lmb_alloc use the above, I don't want 2 implementations of the same thing (maybe call it __lmb_find to expose the fact that it's a low level function to avoid for normal use). Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
