On Mon, Apr 19, 2010 at 9:57 PM, Josef Bacik <josef@xxxxxxxxxx> wrote: > The purpose of maybe_allocate_chunk was that there is no way to know if some > other CPU is currently trying to allocate a chunk for the given space info. We > could have two cpu's come inot do_chunk_alloc at relatively the same time and > end up allocating twice the amount of space, which is why I did the waitqueue > thing. It seems like this is still a possibility with your patch. Thanks, > This is impossible because the very first thing do_chunk_alloc does is lock the chunk_mutex. Yan, Zheng -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
