From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Tal Zussman <tz2294@columbia.edu>,
Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Christian Brauner <brauner@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Carlos Maiolino <cem@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Dave Chinner <dgc@kernel.org>,
Bart Van Assche <bvanassche@acm.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, Gao Xiang <xiang@kernel.org>
Subject: Re: [PATCH v6 1/4] block: add task-context bio completion infrastructure
Date: Wed, 29 Jul 2026 01:48:32 -0700 [thread overview]
Message-ID: <amm-YHQJFUsj4AM6@infradead.org> (raw)
In-Reply-To: <4ahxusvs255ibn5unrayfeioqijbbidtn3l7joczxphwo2faee@3wtnw4nzu6wi>
On Wed, Jul 29, 2026 at 10:41:40AM +0200, Jan Kara wrote:
> This looks a bit hacky and at least deserves a comment. Ideally we'd get
> rid of the xfs workqueue and rely on the generic offloading mechanism. But
> as Christoph wrote maybe let's just get something good enough in and we can
> work on improving that later. In particular if Christoph has a plan how to
> clean this up :).
The XFS workqueue can't just go away, as for writes that require
completion time processing (unwritten extent conversion, i_size logging,
zoned block mapping), we want to serialize the processing on a per-inode
basis as otherwise the different helpers would just content on the xfs
inode lock and burn cycles.
We want to get rid of it for read completions, and a patch for that is
in the lazy bounce series I posted a few days ago.
next prev parent reply other threads:[~2026-07-29 8:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 21:51 [PATCH v6 0/4] block: enable RWF_DONTCACHE for block devices Tal Zussman
2026-05-14 21:51 ` [PATCH v6 1/4] block: add task-context bio completion infrastructure Tal Zussman
2026-05-18 6:48 ` Christoph Hellwig
2026-05-22 22:47 ` Tal Zussman
2026-05-25 5:17 ` Christoph Hellwig
2026-05-26 19:29 ` Tal Zussman
2026-05-27 9:42 ` Jan Kara
2026-05-27 13:00 ` Christoph Hellwig
2026-05-29 20:46 ` Tal Zussman
2026-06-01 11:04 ` Jan Kara
2026-06-18 14:26 ` Jan Kara
2026-06-22 16:45 ` Tal Zussman
2026-07-28 4:10 ` Christoph Hellwig
2026-07-29 6:11 ` Tal Zussman
2026-07-29 6:27 ` Christoph Hellwig
2026-07-29 8:41 ` Jan Kara
2026-07-29 8:48 ` Christoph Hellwig [this message]
2026-05-22 23:09 ` Tal Zussman
2026-05-25 5:24 ` Christoph Hellwig
2026-05-29 8:49 ` Sebastian Andrzej Siewior
2026-05-14 21:51 ` [PATCH v6 2/4] iomap: use BIO_COMPLETE_IN_TASK for dropbehind writeback Tal Zussman
2026-05-18 6:48 ` Christoph Hellwig
2026-05-14 21:51 ` [PATCH v6 3/4] buffer: add dropbehind writeback support Tal Zussman
2026-05-18 6:49 ` Christoph Hellwig
2026-05-22 23:14 ` Tal Zussman
2026-05-25 5:25 ` Christoph Hellwig
2026-05-14 21:51 ` [PATCH v6 4/4] block: enable RWF_DONTCACHE for block devices Tal Zussman
2026-05-18 6:49 ` Christoph Hellwig
2026-05-22 23:17 ` Tal Zussman
2026-05-25 5:30 ` Christoph Hellwig
2026-05-25 18:06 ` 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=amm-YHQJFUsj4AM6@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=bvanassche@acm.org \
--cc=cem@kernel.org \
--cc=dgc@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tz2294@columbia.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=xiang@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