Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: prepare and move async csum generation out of experimental feautres
Date: Tue, 10 Nov 2026 08:33:38 +1030	[thread overview]
Message-ID: <cover.1794261158.git.wqu@suse.com> (raw)

Sashiko exposed several problems related to previous default async csum
generation, one fix related to encoded writes is already merged.

The remaining problem is related to the endio_workers reuse, which can
lead to problems as there are two different workloads in one workqueue,
and one workload (btrfs_bio_csum()) can even queue a new work into the
same workqueue.

The remaining problem is fixed by the first patch, by changing
btrfs_fs_info::workers into a regular workqueue, and let the
experimental csum generation to reuse it.

Then we can finally enable async data csum generation by default to
improve the data write performance, and completely get rid of the old
csum offloading behavior.

Qu Wenruo (2):
  btrfs: make btrfs_fs_info::workers to be a regular workqueue
  btrfs: move async data csum generation out of experimental features

 fs/btrfs/Kconfig     |   2 -
 fs/btrfs/bio.c       | 139 +------------------------------------------
 fs/btrfs/disk-io.c   |  47 ++++++---------
 fs/btrfs/file-item.c |  12 ++--
 fs/btrfs/file-item.h |   2 +-
 fs/btrfs/fs.h        |  17 +-----
 fs/btrfs/super.c     |   2 +-
 7 files changed, 30 insertions(+), 191 deletions(-)

-- 
2.56.0


             reply	other threads:[~2026-11-09 22:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 22:03 Qu Wenruo [this message]
2026-11-09 22:03 ` [PATCH 1/2] btrfs: make btrfs_fs_info::workers to be a regular workqueue Qu Wenruo
2026-11-09 22:03 ` [PATCH 2/2] btrfs: move async data csum generation out of experimental features Qu Wenruo

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=cover.1794261158.git.wqu@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@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