From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <wqu@suse.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Nanzhe Zhao <nzzhao@126.com>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
willy@infradead.org, yi.zhang@huaweicloud.com,
jaegeuk@kernel.org, Chao Yu <chao@kernel.org>,
Barry Song <21cnbao@gmail.com>,
Kundan Kumar <kundan.kumar@samsung.com>
Subject: Re: Iomap and compression? (Was "Re: [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes versus filesystem-specific implementations")
Date: Tue, 24 Feb 2026 06:58:08 -0800 [thread overview]
Message-ID: <aZ28gDfzOd1CSb6M@infradead.org> (raw)
In-Reply-To: <a89cc9a0-37d1-431c-ab98-eed58d5bd93c@suse.com>
On Tue, Feb 24, 2026 at 08:23:35AM +1030, Qu Wenruo wrote:
> > I still think btrfs would benefit greatly from killing the async
> > submission workqueue,
>
> That's for sure. Although without that workqueue, where should the
> compression workload happen?
In the additional writeback threads mentioned below.
> > and I hope that the multiple writeback thread
> > work going on currently will help with this. I think you really should
> > talk to Kundan.
>
> Mind to CC him/her?
Added.
prev parent reply other threads:[~2026-02-24 14:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 12:59 [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes versus filesystem-specific implementations Nanzhe Zhao
2026-02-20 15:48 ` Christoph Hellwig
2026-02-20 18:40 ` Matthew Wilcox
2026-02-23 21:36 ` Jaegeuk Kim
2026-02-26 10:13 ` Barry Song
2026-02-27 2:02 ` Jaegeuk Kim
2026-02-27 2:43 ` Barry Song
2026-02-27 19:25 ` Jaegeuk Kim
2026-02-20 17:07 ` [Lsf-pc] " Jan Kara
2026-02-23 8:34 ` Iomap and compression? (Was "Re: [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes versus filesystem-specific implementations") Qu Wenruo
2026-02-23 13:06 ` Christoph Hellwig
2026-02-23 21:53 ` Qu Wenruo
2026-02-24 14:58 ` Christoph Hellwig [this message]
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=aZ28gDfzOd1CSb6M@infradead.org \
--to=hch@infradead.org \
--cc=21cnbao@gmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kundan.kumar@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=nzzhao@126.com \
--cc=willy@infradead.org \
--cc=wqu@suse.com \
--cc=yi.zhang@huaweicloud.com \
/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