| commit | 9c62110454b088b4914ffe375c2dbc19643eac34 | [log] [tgz] |
|---|---|---|
| author | Jens Axboe <axboe@fb.com> | Tue Mar 14 11:51:59 2017 -0600 |
| committer | Jens Axboe <axboe@fb.com> | Tue Mar 14 11:51:59 2017 -0600 |
| tree | 37f65ae1ac5073f4bf3d31b94b1bc5fc7c706072 | |
| parent | 4a3a485b1ed0e109718cc8c9d094fa0f552de9b2 [diff] |
blk-mq-sched: don't run the queue async from blk_mq_try_issue_directly() If we have scheduling enabled, we jump directly to insert-and-run. That's fine, but we run the queue async and we don't pass in information on whether we can block from this context or not. Fixup both these cases. Reviewed-by: Bart Van Assche <bart.vanassche@sandisk.com> Reviewed-by: Omar Sandoval <osandov@fb.com> Signed-off-by: Jens Axboe <axboe@fb.com>