From: "jianchao.wang" <jianchao.w.wang@oracle.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: ming.lei@redhat.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V9 1/4] blk-mq: insert to hctx dispatch list when bypass_insert is true
Date: Thu, 6 Dec 2018 09:12:02 +0800 [thread overview]
Message-ID: <99339021-4d05-8dff-bee4-a6af2eaf3e21@oracle.com> (raw)
In-Reply-To: <54c7377f-e8e6-92cf-eced-6c76297afd52@kernel.dk>
On 12/6/18 12:25 AM, Jens Axboe wrote:
> On 12/5/18 12:43 AM, Jianchao Wang wrote:
>> We don't allow direct dispatch of anything but regular reads/writes
>> and insert all of non-read-write requests. However, this is not
>> correct for 'bypass_insert == true' case where inserting is ignored
>> and BLK_STS_RESOURCE is returned. The caller will fail forever.
>>
>> Fix it with inserting the non-read-write request to hctx dispatch
>> list to avoid to involve merge and io scheduler when bypass_insert
>> is true.
>>
>> Signed-off-by: Jianchao Wang <jianchao.w.wang@oracle.com>
>> ---
>> block/blk-mq.c | 19 +++++++++++++++++--
>> 1 file changed, 17 insertions(+), 2 deletions(-)
>>
>> diff --git a/block/blk-mq.c b/block/blk-mq.c
>> index 9005505..153af90 100644
>> --- a/block/blk-mq.c
>> +++ b/block/blk-mq.c
>> @@ -1822,6 +1822,7 @@ static blk_status_t __blk_mq_try_issue_directly(struct blk_mq_hw_ctx *hctx,
>> {
>> struct request_queue *q = rq->q;
>> bool run_queue = true;
>> + bool force = false;
>>
>> /*
>> * RCU or SRCU read lock is needed before checking quiesced flag.
>> @@ -1836,9 +1837,19 @@ static blk_status_t __blk_mq_try_issue_directly(struct blk_mq_hw_ctx *hctx,
>> goto insert;
>> }
>>
>> - if (!blk_rq_can_direct_dispatch(rq) || (q->elevator && !bypass_insert))
>> + if (q->elevator && !bypass_insert)
>> goto insert;
>>
>> + if (!blk_rq_can_direct_dispatch(rq)) {
>> + /*
>> + * For 'bypass_insert == true' case, insert request into hctx
>> + * dispatch list.
>> + */
>> + if (bypass_insert)
>> + force = true;
>> + goto insert;
>> + }
>
> Just do force = bypass_insert, no need for the if.
>
Yes, I will do it.
Thanks
Jianchao
next prev parent reply other threads:[~2018-12-06 1:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 7:43 [PATCH V9 0/4] blk-mq: refactor code of issue directly Jianchao Wang
2018-12-05 7:43 ` [PATCH V9 1/4] blk-mq: insert to hctx dispatch list when bypass_insert is true Jianchao Wang
2018-12-05 16:25 ` Jens Axboe
2018-12-06 1:12 ` jianchao.wang [this message]
2018-12-05 7:44 ` [PATCH V9 2/4] blk-mq: refactor the code of issue request directly Jianchao Wang
2018-12-05 16:27 ` Jens Axboe
2018-12-06 1:12 ` jianchao.wang
2018-12-05 7:44 ` [PATCH V9 3/4] blk-mq: issue directly with bypass 'false' in blk_mq_sched_insert_requests Jianchao Wang
2018-12-05 16:30 ` Jens Axboe
2018-12-06 1:11 ` jianchao.wang
2018-12-06 2:13 ` Jens Axboe
2018-12-05 7:44 ` [PATCH V9 4/4] blk-mq: replace and kill blk_mq_request_issue_directly Jianchao Wang
2018-12-05 16:30 ` 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=99339021-4d05-8dff-bee4-a6af2eaf3e21@oracle.com \
--to=jianchao.w.wang@oracle.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®