From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Catherine Hoang <catherine.hoang@oracle.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH v4] xfs: allow read IO and FICLONE to run concurrently
Date: Thu, 19 Oct 2023 23:06:42 -0700 [thread overview]
Message-ID: <ZTIY8jE9vK6A0FE3@infradead.org> (raw)
In-Reply-To: <20231019200411.GN3195650@frogsfrogsfrogs>
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?
next prev parent reply other threads:[~2023-10-20 6:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 20:12 [PATCH v4] xfs: allow read IO and FICLONE to run concurrently Catherine Hoang
2023-10-17 22:59 ` Darrick J. Wong
2023-10-17 23:59 ` Dave Chinner
2023-10-23 6:42 ` Chandan Babu R
2023-10-18 6:08 ` Christoph Hellwig
2023-10-19 20:04 ` Darrick J. Wong
2023-10-20 6:06 ` Christoph Hellwig [this message]
2023-10-20 15:34 ` Darrick J. Wong
2023-10-22 22:42 ` Dave Chinner
2023-10-23 15:40 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZTIY8jE9vK6A0FE3@infradead.org \
--to=hch@infradead.org \
--cc=catherine.hoang@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox