From: Boris Burkov <boris@bur.io>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Selectable checksum implementation
Date: Fri, 29 Jul 2022 10:00:32 -0700 [thread overview]
Message-ID: <YuQSMGYOl8iWqbqn@zen> (raw)
In-Reply-To: <cover.1659106597.git.dsterba@suse.com>
On Fri, Jul 29, 2022 at 04:59:06PM +0200, David Sterba wrote:
> Add a possibility to load accelerated checksum implementation after a
> filesystem has been mounted. Detailed description in patch 3.
What branch is this based on? I am having trouble applying it to
misc-next or for-next.
>
> David Sterba (4):
> btrfs: prepare more slots for checksum shash
> btrfs: assign checksum shash slots on init
> btrfs: add checksum implementation selection after mount
> btrfs: sysfs: print all loaded csums implementations
>
> fs/btrfs/check-integrity.c | 4 +-
> fs/btrfs/compression.c | 4 +-
> fs/btrfs/ctree.h | 13 ++++-
> fs/btrfs/disk-io.c | 30 +++++++----
> fs/btrfs/file-item.c | 4 +-
> fs/btrfs/inode.c | 4 +-
> fs/btrfs/scrub.c | 12 ++---
> fs/btrfs/super.c | 2 -
> fs/btrfs/sysfs.c | 101 +++++++++++++++++++++++++++++++++++--
> 9 files changed, 144 insertions(+), 30 deletions(-)
>
> --
> 2.36.1
>
next prev parent reply other threads:[~2022-07-29 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 14:59 [PATCH 0/4] Selectable checksum implementation David Sterba
2022-07-29 14:59 ` [PATCH 1/4] btrfs: prepare more slots for checksum shash David Sterba
2022-07-29 14:59 ` [PATCH 2/4] btrfs: assign checksum shash slots on init David Sterba
2022-07-29 14:59 ` [PATCH 3/4] btrfs: add checksum implementation selection after mount David Sterba
2022-07-29 14:59 ` [PATCH 4/4] btrfs: sysfs: print all loaded csums implementations David Sterba
2022-07-29 17:00 ` Boris Burkov [this message]
2022-07-29 17:23 ` [PATCH 0/4] Selectable checksum implementation David Sterba
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=YuQSMGYOl8iWqbqn@zen \
--to=boris@bur.io \
--cc=dsterba@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 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.