[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1682088075.git.dsterba@suse.com>
Date: Fri, 21 Apr 2023 17:21:31 +0200
From: David Sterba <dsterba@...e.com>
To: torvalds@...ux-foundation.org
Cc: David Sterba <dsterba@...e.com>, linux-btrfs@...r.kernel.org,
linux-kernel@...r.kernel.org, regressions@...ts.linux.dev
Subject: [GIT PULL] Btrfs fixes for 6.3-rc8
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(-)
Powered by blists - more mailing lists