Message ID | 20231227092305.279567-4-hch@lst.de (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [1/4] null_blk: don't cap max_hw_sectors to BLK_DEF_MAX_SECTORS | expand |
diff --git a/drivers/block/loop.c b/drivers/block/loop.c index 9f2d412fc560e1..6106303fcc4677 100644 --- a/drivers/block/loop.c +++ b/drivers/block/loop.c @@ -2038,7 +2038,8 @@ static int loop_add(int i) } lo->lo_queue = lo->lo_disk->queue; - blk_queue_max_hw_sectors(lo->lo_queue, BLK_DEF_MAX_SECTORS); + /* random number picked from the history block max_sectors cap */ + blk_queue_max_hw_sectors(lo->lo_queue, 2560u); /* * By default, we do buffer IO, so it doesn't make sense to enable
BLK_DEF_MAX_SECTORS despite the confusing name is the default cap for the max_sectors limits. Don't use it to initialize max_hw_setors, which is a hardware / driver capacility. Signed-off-by: Christoph Hellwig <hch@lst.de> --- drivers/block/loop.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)