mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Daniel Vacek <neelx@suse.com>, David Sterba <dsterba@suse.com>,
	Chris Mason <mason@kernel.org>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] btrfs: promote async checksumming out of EXPERIMENTAL
Date: Thu, 3 Sep 2026 16:03:57 +0930	[thread overview]
Message-ID: <a9179480-4f99-407d-b381-5c97a1e85a2d@suse.com> (raw)
In-Reply-To: <20260903062317.3928665-4-neelx@suse.com>



在 2026/9/3 15:53, Daniel Vacek 写道:
> There was no issue with this feature since it's introduction in
> dd57c78aec398 ("btrfs: introduce btrfs_bio::async_csum").
> No need for hiding it.
> 
> Signed-off-by: Daniel Vacek <neelx@suse.com>

Oh, I was doing this already, and it turns out that we have a lot of 
things to cleanup:

---
  fs/btrfs/bio.c       | 136 +------------------------------------------
  fs/btrfs/disk-io.c   |  20 +------
  fs/btrfs/file-item.c |   6 +-
  fs/btrfs/file-item.h |   2 +-
  fs/btrfs/fs.h        |  10 ----
  fs/btrfs/super.c     |   1 -
  6 files changed, 4 insertions(+), 171 deletions(-)

The main missing part is the should_async_write() now always return 
false (you missed that EXPERIMENTAL flag there).

Then it means the whole async submission part is no longer required, 
resulting the above code removal.

Thanks,
Qu


> ---
> 
> v2: Introduced this change.
> ---
>   fs/btrfs/bio.c | 4 ----
>   1 file changed, 4 deletions(-)
> 
> diff --git a/fs/btrfs/bio.c b/fs/btrfs/bio.c
> index 771b7d598aee..db426ee6e587 100644
> --- a/fs/btrfs/bio.c
> +++ b/fs/btrfs/bio.c
> @@ -569,11 +569,7 @@ static int btrfs_bio_csum(struct btrfs_bio *bbio)
>   {
>   	if (bbio->bio.bi_opf & REQ_META)
>   		return btree_csum_one_bio(bbio);
> -#ifdef CONFIG_BTRFS_EXPERIMENTAL
>   	return btrfs_csum_one_bio(bbio, true);
> -#else
> -	return btrfs_csum_one_bio(bbio, false);
> -#endif
>   }
>   
>   /*


  reply	other threads:[~2026-09-03  6:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  6:23 [PATCH v2 0/3] btrfs: async checksumming cleanups Daniel Vacek
2026-09-03  6:23 ` [PATCH v2 1/3] btrfs: consume the given iter directly instead of copying in csum_one_bio() Daniel Vacek
2026-09-03  6:45   ` Qu Wenruo
2026-09-03  6:23 ` [PATCH v2 2/3] btrfs: use bio::remaining for async checksumming synchronization Daniel Vacek
2026-09-04 22:41   ` Qu Wenruo
2026-09-04 22:50     ` Qu Wenruo
2026-09-03  6:23 ` [PATCH v2 3/3] btrfs: promote async checksumming out of EXPERIMENTAL Daniel Vacek
2026-09-03  6:33   ` Qu Wenruo [this message]
2026-09-03  6:41     ` Daniel Vacek

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=a9179480-4f99-407d-b381-5c97a1e85a2d@suse.com \
    --to=wqu@suse.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@kernel.org \
    --cc=neelx@suse.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

all inboxes | Powered by JetHome®