On Thu, Oct 19, 2023 at 01:04:11PM -0700, Darrick J. Wong wrote: > Well... the stupid answer is that I augmented generic/176 to try to race > buffered and direct reads with cloning a million extents and print out > when the racing reads completed. On an unpatched kernel, the reads > don't complete until the reflink does: > So as you can see, reads from the reflink source file no longer > experience a giant latency spike. I also wrote an fstest to check this > behavior; I'll attach it as a separate reply. Nice. I guess write latency doesn't really matter for this use case?
