diff options
| author | Yu Kuai <[email protected]> | 2025-05-24 06:13:11 +0000 |
|---|---|---|
| committer | Yu Kuai <[email protected]> | 2025-05-30 07:47:23 +0000 |
| commit | b886475804230cad8075e1ed8c7fb2333f7c41c1 (patch) | |
| tree | 5091efda1c9a85147c22a5edf9ef1d8af72819d0 /drivers/md/dm-raid.c | |
| parent | md/md-bitmap: fix dm-raid max_write_behind setting (diff) | |
| download | kernel-b886475804230cad8075e1ed8c7fb2333f7c41c1.tar.gz kernel-b886475804230cad8075e1ed8c7fb2333f7c41c1.zip | |
md/dm-raid: remove max_write_behind setting limit
The comments said 'vaule in kB', while the value actually means the
number of write_behind IOs. And since md-bitmap will automatically
adjust the value to max COUNTER_MAX / 2, there is no need to fail
early.
Also move some macros that is only used md-bitmap.c.
Link: https://lore.kernel.org/linux-raid/[email protected]
Signed-off-by: Yu Kuai <[email protected]>
Reviewed-by: Christoph Hellwig <[email protected]>
Reviewed-by: Hannes Reinecke <[email protected]>
Reviewed-by: Xiao Ni <[email protected]>
Diffstat (limited to 'drivers/md/dm-raid.c')
| -rw-r--r-- | drivers/md/dm-raid.c | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/drivers/md/dm-raid.c b/drivers/md/dm-raid.c index 127138c61be5..d296770478b2 100644 --- a/drivers/md/dm-raid.c +++ b/drivers/md/dm-raid.c @@ -1356,11 +1356,7 @@ static int parse_raid_params(struct raid_set *rs, struct dm_arg_set *as, return -EINVAL; } - /* - * In device-mapper, we specify things in sectors, but - * MD records this value in kB - */ - if (value < 0 || value / 2 > COUNTER_MAX) { + if (value < 0) { rs->ti->error = "Max write-behind limit out of range"; return -EINVAL; } |