On Mon, Oct 16, 2017 at 09:00:19AM +1100, Dave Chinner wrote: > fallocate will block *all* IO and mmap faults on that file, not just > the ones that require allocation. fallocate creates a complete IO > submission pipeline stall, punting all new IO submissions to the > background worker where they will block until fallocate completes. Not sure if it helps Avis case, but I think we could relax the fallocate exclusive i_rwsem requirement a bit, similar to direct I/O writes. Basically as long as your fallocate is block aligned we should be fine with a shared iolock for the "normal" allocating fallocate (discounting things like hole punches and extent shifts of course). -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
