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,
regressions@lists.linux.dev
Subject: [GIT PULL] Btrfs fixes for 6.3-rc8
Date: Fri, 21 Apr 2023 17:21:31 +0200 [thread overview]
Message-ID: <cover.1682088075.git.dsterba@suse.com> (raw)
Hi,
two patches fixing the problem with aync discard. The default settings
had a low IOPS limit and processing a large batch to discard would take
a long time. On laptops this can cause increased power consumption due
to disk activity. As async discard has been on by default since 6.2 this
likely affects a lot of users.
Please pull, thanks.
- increase the default IOPS limit 10x which reportedly helped
- setting the sysfs IOPS value to 0 now does not throttle anymore
allowing the discards to be processed at full speed, previously there
was an arbitrary 6 hour target for processing the pending batch
----------------------------------------------------------------
The following changes since commit 68d99ab0e9221ef54506f827576c5a914680eeaf:
btrfs: fix fast csum implementation detection (2023-04-06 16:34:13 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.3-rc7-tag
for you to fetch changes up to ef9cddfe57d86aac6b509b550136395669159b30:
btrfs: reinterpret async discard iops_limit=0 as no delay (2023-04-21 00:28:23 +0200)
----------------------------------------------------------------
Boris Burkov (2):
btrfs: set default discard iops_limit to 1000
btrfs: reinterpret async discard iops_limit=0 as no delay
fs/btrfs/discard.c | 21 +++++++++++++--------
1 file changed, 13 insertions(+), 8 deletions(-)
next reply other threads:[~2023-04-21 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 15:21 David Sterba [this message]
2023-04-21 18:15 ` [GIT PULL] Btrfs fixes for 6.3-rc8 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.1682088075.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--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