summaryrefslogtreecommitdiff
path: root/drivers/block/virtio_blk.c
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2017-06-19 10:26:24 +0300
committerJens Axboe <axboe@kernel.dk>2017-06-27 21:13:45 +0300
commit46685d1a9521054fa3a7a352f6bb54166cd5b2c5 (patch)
tree4da41c3661d2fc577ff72d36ab53e64c8d803c62 /drivers/block/virtio_blk.c
parent0b0bcacc3b4300c4bba0bacb4c7a279b2728f331 (diff)
downloadlinux-46685d1a9521054fa3a7a352f6bb54166cd5b2c5.tar.xz
blk-mq: don't bounce by default
For historical reasons we default to bouncing highmem pages for all block queues. But the blk-mq drivers are easy to audit to ensure that we don't need this - scsi and mtip32xx set explicit limits and everyone else doesn't have any particular ones. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/block/virtio_blk.c')
-rw-r--r--drivers/block/virtio_blk.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
index e59bd4549a8a..0297ad7c1452 100644
--- a/drivers/block/virtio_blk.c
+++ b/drivers/block/virtio_blk.c
@@ -720,9 +720,6 @@ static int virtblk_probe(struct virtio_device *vdev)
/* We can handle whatever the host told us to handle. */
blk_queue_max_segments(q, vblk->sg_elems-2);
- /* No need to bounce any requests */
- blk_queue_bounce_limit(q, BLK_BOUNCE_ANY);
-
/* No real sector limit. */
blk_queue_max_hw_sectors(q, -1U);