diff options
author | 2023-04-21 10:47:21 -0700 | |
---|---|---|
committer | 2023-04-21 10:47:21 -0700 | |
commit | c337b23f32c87320dffd389e4f0f793db35f0a9b (patch) | |
tree | 2b7f2296ca48d77e1642511eed2601e0f5b94508 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Merge tag 'block-6.3-2023-04-21' of git://git.kernel.dk/linux (diff) | |
parent | btrfs: reinterpret async discard iops_limit=0 as no delay (diff) | |
download | wireguard-linux-c337b23f32c87320dffd389e4f0f793db35f0a9b.tar.xz wireguard-linux-c337b23f32c87320dffd389e4f0f793db35f0a9b.zip |
Merge tag 'for-6.3-rc7-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
Pull btrfs fixes from David Sterba:
"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.
Summary:
- 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"
* tag 'for-6.3-rc7-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux:
btrfs: reinterpret async discard iops_limit=0 as no delay
btrfs: set default discard iops_limit to 1000
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions