All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: axboe@kernel.dk
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com
Subject: [PATCH 06/10] blk-mq: don't bounce by default
Date: Mon, 19 Jun 2017 09:26:24 +0200	[thread overview]
Message-ID: <20170619072628.12894-7-hch@lst.de> (raw)
In-Reply-To: <20170619072628.12894-1-hch@lst.de>

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>
---
 block/blk-mq.c               | 5 -----
 drivers/block/virtio_blk.c   | 3 ---
 drivers/block/xen-blkfront.c | 3 ---
 3 files changed, 11 deletions(-)

diff --git a/block/blk-mq.c b/block/blk-mq.c
index e26b7435e245..dd276a9e138e 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -2300,11 +2300,6 @@ struct request_queue *blk_mq_init_allocated_queue(struct blk_mq_tag_set *set,
 	blk_queue_make_request(q, blk_mq_make_request);
 
 	/*
-	 * by default assume old behaviour and bounce for any highmem page
-	 */
-	blk_queue_bounce_limit(q, BLK_BOUNCE_HIGH);
-
-	/*
 	 * Do this after blk_queue_make_request() overrides it...
 	 */
 	q->nr_requests = set->queue_depth;
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);
 
diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
index ac90093fcb25..c852ed3c01d5 100644
--- a/drivers/block/xen-blkfront.c
+++ b/drivers/block/xen-blkfront.c
@@ -953,9 +953,6 @@ static void blkif_set_queue_limits(struct blkfront_info *info)
 
 	/* Make sure buffer addresses are sector-aligned. */
 	blk_queue_dma_alignment(rq, 511);
-
-	/* Make sure we don't use bounce buffers. */
-	blk_queue_bounce_limit(rq, BLK_BOUNCE_ANY);
 }
 
 static int xlvbd_init_blk_queue(struct gendisk *gd, u16 sector_size,
-- 
2.11.0

  parent reply	other threads:[~2017-06-19  7:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19  7:26 move bounce limits settings into the drivers Christoph Hellwig
2017-06-19  7:26 ` [PATCH 01/10] pktcdvd: remove the call to blk_queue_bounce Christoph Hellwig
2017-06-19 14:34   ` Ming Lei
2017-06-19 15:00     ` Christoph Hellwig
2017-06-19 15:00       ` Christoph Hellwig
2017-06-19 15:13       ` Ming Lei
2017-06-19 15:18         ` Christoph Hellwig
2017-06-19 15:18           ` Christoph Hellwig
2017-06-19 15:29           ` Ming Lei
2017-06-19  7:26 ` [PATCH 02/10] blk-map: call blk_queue_bounce from blk_rq_append_bio Christoph Hellwig
2017-06-19  7:26 ` [PATCH 03/10] block: move bounce declarations to block/blk.h Christoph Hellwig
2017-06-19  7:26 ` [PATCH 04/10] block: remove the queue_bounce_pfn helper Christoph Hellwig
2017-06-19  7:26 ` [PATCH 05/10] block: don't bother with bounce limits for make_request drivers Christoph Hellwig
2017-06-19  7:26 ` Christoph Hellwig [this message]
2017-06-19  7:26 ` [PATCH 07/10] block: don't set bounce limit in blk_init_allocated_queue Christoph Hellwig
2017-06-19  7:26 ` [PATCH 08/10] block: don't set bounce limit in blk_init_queue Christoph Hellwig
2017-06-19  7:26 ` [PATCH 09/10] dm: don't set bounce limit Christoph Hellwig
2017-06-19  7:26 ` [PATCH 10/10] mmc/block: remove a call to blk_queue_bounce_limit Christoph Hellwig
2017-06-26 10:00 ` move bounce limits settings into the drivers Christoph Hellwig
2017-06-27 18:10 ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170619072628.12894-7-hch@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=linux-block@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.