Josef Bacik wrote: > 3) Lock the entire range during DIO. I originally had it so we would lock the > extents as get_block was called, and then unlock them as the endio function > was > called, which worked great, but if we ever had an error in the submit_io hook, > we could have locked an extent that would never be submitted for IO, so we > wouldn't be able to unlock it, so this solution fixed that problem and made > it a > bit cleaner.
Does this prevent concurrent DIOs to overlapping or nearby ranges? Thanks, -- Jamie -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
