diff options
author | Ming Lei <ming.lei@redhat.com> | 2017-11-02 23:24:36 +0800 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2017-11-04 12:38:50 -0600 |
commit | a6a252e6491443c1c18eab7e254daee63d4a7a04 (patch) | |
tree | e87705015ce4b4722e271acf2f99db7dfdfe7d2d /kernel | |
parent | 598906f814280762157629ba8833bf5cb11def74 (diff) | |
download | linux-a6a252e6491443c1c18eab7e254daee63d4a7a04.tar.gz linux-a6a252e6491443c1c18eab7e254daee63d4a7a04.tar.bz2 linux-a6a252e6491443c1c18eab7e254daee63d4a7a04.zip |
blk-mq-sched: decide how to handle flush rq via RQF_FLUSH_SEQ
In case of IO scheduler we always pre-allocate one driver tag before
calling blk_insert_flush(), and flush request will be marked as
RQF_FLUSH_SEQ once it is in flush machinery.
So if RQF_FLUSH_SEQ isn't set, we call blk_insert_flush() to handle
the request, otherwise the flush request is dispatched to ->dispatch
list directly.
This is a preparation patch for not preallocating a driver tag for flush
requests, and for not treating flush requests as a special case. This is
similar to what the legacy path does.
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions