From c7616924f111ba3a65541e039a7aec6ad05fd790 Mon Sep 17 00:00:00 2001 From: Andrew Morton <akpm@digeo.com> Date: Wed, 11 Jun 2003 06:44:47 -0700 Subject: [PATCH] [PATCH] loop: remove blk_queue_bounce From: Hugh Dickins <hugh@veritas.com> What purpose does loop_make_request's blk_queue_bounce serve? None, it's just a relic from before the kmaps were added to loop's transfers, and ties up mempooled resources - in the file-backed case, with no guarantee they'll soon be freed. And what purpose does loop_set_fd's blk_queue_bounce_limit serve? None, blk_queue_make_request did that. --- drivers/block/loop.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/block/loop.c b/drivers/block/loop.c index ddcc779cd388..46399bdd0d73 100644 --- a/drivers/block/loop.c +++ b/drivers/block/loop.c @@ -548,8 +548,6 @@ static int loop_make_request(request_queue_t *q, struct bio *old_bio) goto err; } - blk_queue_bounce(q, &old_bio); - /* * file backed, queue for loop_thread to handle */ @@ -742,7 +740,6 @@ static int loop_set_fd(struct loop_device *lo, struct file *lo_file, * device */ blk_queue_make_request(&lo->lo_queue, loop_make_request); - blk_queue_bounce_limit(&lo->lo_queue, BLK_BOUNCE_HIGH); lo->lo_queue.queuedata = lo; /* -- 2.30.9