All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vacek <neelx@suse.com>
To: David Sterba <dsterba@suse.com>, Chris Mason <mason@kernel.org>
Cc: Daniel Vacek <neelx@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Qu Wenruo <wqu@suse.com>
Subject: [PATCH 0/2] btrfs: async checksumming cleanups
Date: Wed,  2 Sep 2026 18:51:34 +0200	[thread overview]
Message-ID: <20260902165137.3781696-1-neelx@suse.com> (raw)

While trying to deal with encryption bounce bios checksumming, a solution
came up which covers all writes (also the regular !encrypted ones). As a
result the code cleans up quite nicely. That's the second patch in this
series. The first one is just a nit. Details in the patches themselves.

Daniel Vacek (2):
  btrfs: consume the given iter directly instead of copying in
    csum_one_bio()
  btrfs: use bio::remaining for async checksumming synchronization

 fs/btrfs/bio.c       |  4 ----
 fs/btrfs/bio.h       |  4 ----
 fs/btrfs/file-item.c | 20 +++++++++-----------
 3 files changed, 9 insertions(+), 19 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-09-02 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 16:51 Daniel Vacek [this message]
2026-09-02 16:51 ` [PATCH 1/2] btrfs: consume the given iter directly instead of copying in csum_one_bio() Daniel Vacek
2026-09-02 21:51   ` Qu Wenruo
2026-09-02 22:47     ` Qu Wenruo
2026-09-03  4:49   ` Daniel Vacek
2026-09-02 16:51 ` [PATCH 2/2] btrfs: use bio::remaining for async checksumming synchronization Daniel Vacek
2026-09-02 22:02   ` Qu Wenruo
2026-09-02 22:20     ` 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=20260902165137.3781696-1-neelx@suse.com \
    --to=neelx@suse.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@kernel.org \
    --cc=wqu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.