diff options
author | Coly Li <colyli@suse.de> | 2018-12-13 22:53:55 +0800 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2018-12-13 08:15:54 -0700 |
commit | 9aaf51654672b16566c5fe787da3ca41ebf6d297 (patch) | |
tree | 677dc8022feb884c09326c0d940d00c2a7385bbc /net | |
parent | 009673d02fa92acaa7ed0b1e1389610e4390ba49 (diff) | |
download | linux-9aaf51654672b16566c5fe787da3ca41ebf6d297.tar.bz2 |
bcache: make cutoff_writeback and cutoff_writeback_sync tunable
Currently the cutoff writeback and cutoff writeback sync thresholds are
defined by CUTOFF_WRITEBACK (40) and CUTOFF_WRITEBACK_SYNC (70) as
static values. Most of time these they work fine, but when people want
to do research on bcache writeback mode performance tuning, there is no
chance to modify the soft and hard cutoff writeback values.
This patch introduces two module parameters bch_cutoff_writeback_sync
and bch_cutoff_writeback which permit people to tune the values when
loading bcache.ko. If they are not specified by module loading, current
values CUTOFF_WRITEBACK_SYNC and CUTOFF_WRITEBACK will be used as
default and nothing changes.
When people want to tune this two values,
- cutoff_writeback can be set in range [1, 70]
- cutoff_writeback_sync can be set in range [1, 90]
- cutoff_writeback always <= cutoff_writeback_sync
The default values are strongly recommended to most of users for most of
workloads. Anyway, if people wants to take their own risk to do research
on new writeback cutoff tuning for their own workload, now they can make
it.
Signed-off-by: Coly Li <colyli@suse.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions