On Tue, Sep 18, 2012 at 01:00:58AM +0400, Andrey Sidorov wrote: > Improve mb_free_blocks speed by clearing bits all at once instead of > going one by one. Rebuild buddy bitmap by going up only once per range > instead of once per block. > This algorithm relies on buddy bitmap to be correct and it can't > handle ranges with already freed blocks producing incorrect results in > these conditions. > I will add checking for error cases is to be added as soon as I get > some inputs on how to do that (and if this patch has some interest at > all). Thanks, this patch is interesting as well --- but yes, we do need to make sure the changes will not make any potential inconsistency in the buddy bitmaps any worse that they already are. The main thing we need to consider for the buddy bitmap code is that it's one of the more subtle and complex bits of code in the ext4 code base. So changing it is always scary that there is some interesting edge case that isn't quite right. That means the two things we need to consider are (a) adding sanity checking code which we can compile in or out to test to make sure the right thing happens for all of the various corner cases, and (b) making sure we do the right thing even if the buddy bitmaps have gotten corrupted in memory some how. Regards, - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
