diff options
| author | Christoph Hellwig <[email protected]> | 2022-04-18 06:53:06 +0200 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2022-05-03 10:38:50 -0600 |
| commit | fb749a87f4536d2fa86ea135ae4eff1072903438 (patch) | |
| tree | c504d09ac29d71d0e7fe99da37f0a35c4cad6fe2 | |
| parent | 4a04d517c56e0616c6f69afc226ee2691e543712 (diff) | |
null_blk: don't set the discard_alignment queue limit
The discard_alignment queue limit is named a bit misleading means the
offset into the block device at which the discard granularity starts.
Setting it to the discard granularity as done by null_blk is mostly
harmless but also useless.
Signed-off-by: Christoph Hellwig <[email protected]>
Reviewed-by: Damien Le Moal <[email protected]>
Reviewed-by: Chaitanya Kulkarni <[email protected]>
Reviewed-by: Martin K. Petersen <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jens Axboe <[email protected]>
| -rw-r--r-- | drivers/block/null_blk/main.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/block/null_blk/main.c b/drivers/block/null_blk/main.c index 5cb4c92cdffe..a521e914a984 100644 --- a/drivers/block/null_blk/main.c +++ b/drivers/block/null_blk/main.c @@ -1765,7 +1765,6 @@ static void null_config_discard(struct nullb *nullb) } nullb->q->limits.discard_granularity = nullb->dev->blocksize; - nullb->q->limits.discard_alignment = nullb->dev->blocksize; blk_queue_max_discard_sectors(nullb->q, UINT_MAX >> 9); } |