block: move queue run on unplug to kblockd

There are worries that we are now consuming a lot more stack in some cases, since we potentially call into IO dispatch from schedule() or io_schedule(). We can reduce this problem by moving the running of the queue to kblockd, like the old plugging scheme did as well. This may or may not be a good idea from a performance perspective, depending on how many tasks have queue plugs running at the same time. For even the slightly contended case, doing just a single queue run from kblockd instead of multiple runs directly from the unpluggers will be faster. Signed-off-by: Jens Axboe <[email protected]> --- yaml --- svn_rev: 244103 current_ref: refs/heads/rpi-3.12.y current_commit: f4af3c3 head_branch: refs/heads/rpi-3.12.y migrated_from: v3
koalo · Apr 12, 2011 · 5654720 · 5654720
1 parent cf2d02a
commit 5654720
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/rpi-3.12.y: cf82c798394cd443eed7d91f998b79a63f341e91
+refs/heads/rpi-3.12.y: f4af3c3d077a004762aaad052049c809fd8c6f0c
diff --git a/trunk/block/blk-core.c b/trunk/block/blk-core.c
@@ -2665,7 +2665,7 @@ static int plug_rq_cmp(void *priv, struct list_head *a, struct list_head *b)
 static void queue_unplugged(struct request_queue *q, unsigned int depth)
 {
 	trace_block_unplug_io(q, depth);
-	__blk_run_queue(q, false);
+	__blk_run_queue(q, true);
 
 	if (q->unplugged_fn)
 		q->unplugged_fn(q);