diff options
author | Christoph Böhmwalder <christoph.boehmwalder@linbit.com> | 2022-11-09 16:34:51 +0300 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2022-11-09 22:40:36 +0300 |
commit | 258bea6388ac93f34561fd91064232d14e174bff (patch) | |
tree | cad4a7afa10d1222315d5f5f002acc8c0ffce435 /tools/perf/scripts/python/syscall-counts.py | |
parent | 6d4338cb4070a762dba0cadee00b7ec206d9f868 (diff) | |
download | linux-258bea6388ac93f34561fd91064232d14e174bff.tar.xz |
drbd: use blk_queue_max_discard_sectors helper
We currently only set q->limits.max_discard_sectors, but that is not
enough. Another field, max_hw_discard_sectors, was introduced in
commit 0034af036554 ("block: make /sys/block/<dev>/queue/discard_max_bytes
writeable").
The difference is that max_discard_sectors can be changed from user
space via sysfs, while max_hw_discard_sectors is the "hardware" upper
limit.
So use this helper, which sets both.
This is also a fixup for commit 998e9cbcd615 ("drbd: cleanup
decide_on_discard_support"): if discards are not supported, that does
not necessarily mean we also want to disable write_zeroes.
Fixes: 998e9cbcd615 ("drbd: cleanup decide_on_discard_support")
Reviewed-by: Joel Colledge <joel.colledge@linbit.com>
Signed-off-by: Christoph Böhmwalder <christoph.boehmwalder@linbit.com>
Link: https://lore.kernel.org/r/20221109133453.51652-2-christoph.boehmwalder@linbit.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions