From: "Darrick J. Wong" <djwong@kernel.org>
To: Tal Zussman <tz2294@columbia.edu>
Cc: Carlos Maiolino <cem@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>, Jan Kara <jack@suse.cz>,
linux-block@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: avoid double deferrals for RWF_DONTCACHE writes
Date: Mon, 10 Aug 2026 11:33:41 -0700 [thread overview]
Message-ID: <20260810183341.GZ3556460@frogsfrogsfrogs> (raw)
In-Reply-To: <20260810-xfs-dontcache-double-defer-v1-1-aea7484b3e49@columbia.edu>
On Mon, Aug 10, 2026 at 12:39:19PM -0400, Tal Zussman wrote:
> XFS already defers some writes to a workqueue when transactions are
> needed to process the I/O completion. Disable the block layer bio task
> completion in this case to avoid a major performance drop.
>
> Fixes: efbde6f9f449 ("iomap: use BIO_COMPLETE_IN_TASK for dropbehind writeback")
What commit is this?
(If we're fixing something that's not in Linus' tree then I think the
fixes tags aren't required)
> Link: https://lore.kernel.org/all/8124341f-3af2-4a16-897d-38db5ab5a9d4@columbia.edu/
> Signed-off-by: Tal Zussman <tz2294@columbia.edu>
> ---
> Follow-up fix for the RWF_DONTCACHE task-completion series. This is
> targeting the block tree. [1]
>
> [1]: https://lore.kernel.org/linux-block/annkDbhXBEeMoNVT@infradead.org/
> ---
> fs/xfs/xfs_aops.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
> index cd8de8c82d78..74a6089abadf 100644
> --- a/fs/xfs/xfs_aops.c
> +++ b/fs/xfs/xfs_aops.c
> @@ -549,10 +549,14 @@ xfs_writeback_submit(
> }
>
> /*
> - * Send ioends that might require a transaction to the completion wq.
> + * Send ioends that might require a transaction to the completion wq,
> + * and disable the block layer task completion for them as there is no
> + * need to defer twice.
> */
> - if (xfs_ioend_needs_wq_completion(ioend))
> + if (xfs_ioend_needs_wq_completion(ioend)) {
> ioend->io_bio.bi_end_io = xfs_end_bio;
> + bio_clear_flag(&ioend->io_bio, BIO_COMPLETE_IN_TASK);
> + }
>
> return iomap_ioend_writeback_submit(wpc, error);
> }
> @@ -663,7 +667,14 @@ xfs_zoned_writeback_submit(
> {
> struct iomap_ioend *ioend = wpc->wb_ctx;
>
> + /*
> + * Defer all completions to our workqueue as all zoned writes require a
> + * transaction to be persisted. This also means we never need the block
> + * layer in-task completion for a task context.
> + */
> ioend->io_bio.bi_end_io = xfs_end_bio;
> + bio_clear_flag(&ioend->io_bio, BIO_COMPLETE_IN_TASK);
This makes sense to me;
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> +
> if (error) {
> ioend->io_bio.bi_status = errno_to_blk_status(error);
> bio_endio(&ioend->io_bio);
>
> ---
> base-commit: 30df3ab3c92d0e7854c54df6ae66f4aa6eb5b3d2
> change-id: 20260810-xfs-dontcache-double-defer-ae3fa50ba02c
>
> Best regards,
> --
> Tal Zussman <tz2294@columbia.edu>
>
>
next prev parent reply other threads:[~2026-08-10 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 16:39 [PATCH] xfs: avoid double deferrals for RWF_DONTCACHE writes Tal Zussman
2026-08-10 17:37 ` Christoph Hellwig
2026-08-10 18:33 ` Darrick J. Wong [this message]
2026-08-11 11:43 ` Tal Zussman
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=20260810183341.GZ3556460@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=axboe@kernel.dk \
--cc=cem@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tz2294@columbia.edu \
/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