diff options
| author |  Bart Van Assche <bvanassche@acm.org>
| 2024-03-13 14:42:18 -0700 |
|---|---|---|
| committer |  Jens Axboe <axboe@kernel.dk>
| 2024-03-13 15:56:14 -0600 |
| commit | 256aab46e31683d76d45ccbedc287b4d3f3e322b (patch) | |
| tree | 68f53d685ad63a8239a06b258b1035ef2e7a9032 /block/blk-cgroup.c | |
| parent | block: limit block time caching to in_task() context (diff) | |
| download | linux-256aab46e31683d76d45ccbedc287b4d3f3e322b.tar.gz linux-256aab46e31683d76d45ccbedc287b4d3f3e322b.tar.bz2 linux-256aab46e31683d76d45ccbedc287b4d3f3e322b.zip | |
Revert "block/mq-deadline: use correct way to throttling write requests"
The code "max(1U, 3 * (1U << shift) / 4)" comes from the Kyber I/O
scheduler. The Kyber I/O scheduler maintains one internal queue per hwq
and hence derives its async_depth from the number of hwq tags. Using
this approach for the mq-deadline scheduler is wrong since the
mq-deadline scheduler maintains one internal queue for all hwqs
combined. Hence this revert.
Cc: stable@vger.kernel.org
Cc: Damien Le Moal <dlemoal@kernel.org>
Cc: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: Zhiguo Niu <Zhiguo.Niu@unisoc.com>
Fixes: d47f9717e5cf ("block/mq-deadline: use correct way to throttling write requests")
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Link: https://lore.kernel.org/r/20240313214218.1736147-1-bvanassche@acm.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-cgroup.c')
0 files changed, 0 insertions, 0 deletions