The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 6.3-rc7
Date: Tue, 11 Apr 2023 20:12:23 +0200	[thread overview]
Message-ID: <cover.1681236364.git.dsterba@suse.com> (raw)

Hi,

two more fixes that have some user visible effects. Please pull, thanks.

- fix fast checksum detection, this affects filesystems with non-crc32c
  checksum, calculation would not be offloaded to worker threads

- restore thread_pool mount option behaviour for endio workers, the
  new value for maximum active threads would not be set to the actual
  work queues

----------------------------------------------------------------
The following changes since commit 2280d425ba3599bdd85c41bd0ec8ba568f00c032:

  btrfs: ignore fiemap path cache when there are multiple paths for a node (2023-03-29 01:16:23 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.3-rc6-tag

for you to fetch changes up to 68d99ab0e9221ef54506f827576c5a914680eeaf:

  btrfs: fix fast csum implementation detection (2023-04-06 16:34:13 +0200)

----------------------------------------------------------------
Christoph Hellwig (2):
      btrfs: restore the thread_pool= behavior in remount for the end I/O workqueues
      btrfs: fix fast csum implementation detection

 fs/btrfs/disk-io.c | 14 ++++++++++++++
 fs/btrfs/super.c   |  4 ++--
 2 files changed, 16 insertions(+), 2 deletions(-)

             reply	other threads:[~2023-04-11 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 18:12 David Sterba [this message]
2023-04-11 18:52 ` [GIT PULL] Btrfs fixes for 6.3-rc7 pr-tracker-bot

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.1681236364.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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