From: Jianchao Wang <jianchao.w.wang@oracle.com>
To: axboe@kernel.dk
Cc: ming.lei@redhat.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH RESENT V3 0/4] blk-mq: refactor and fix on issue request directly
Date: Mon, 29 Oct 2018 16:49:07 +0800 [thread overview]
Message-ID: <1540802951-5408-1-git-send-email-jianchao.w.wang@oracle.com> (raw)
Hi Jens
The 1st patch refactors the code of issue request directly.
It merges the blk_mq_try_issue_directly and __blk_mq_try_issue_directly
and make it handle the return value of .queue_rq itself.
The 2nd patch let the requests be inserted into hctx->dispatch when
the queue is stopped or quiesced if bypass_insert is true.
The 3rd patch make blk_mq_sched_insert_requests issue requests directly
with 'bypass_insert' false, then it needn't to handle the non-issued requests
any more.
The 4th patch ensures the hctx to be ran on its mapped cpu in issue directly
path.
V3:
- Correct the code about the case bypass_insert is true and io scheduler
attached. The request still need to be issued in case above. (1/4)
- Refactor the code to make code clearer. blk_mq_make_request is introduced
to decide insert, end or just return based on the return value of .queue_rq
and bypass_insert (1/4)
- Add the 2nd patch. It introduce a new decision result which indicates to
insert request with blk_mq_request_bypass_insert.
- Modify the code to adapt the new patch 1.
V2:
- Add 1st and 2nd patch
Jianchao Wang(4)
blk-mq: refactor the code of issue request directly
blk-mq: insert request without involving any io
blk-mq: issue directly with bypass_insert 'false' in
blk-mq: ensure hctx to be ran on mapped cpu when issue
block/blk-mq-sched.c | 8 ++-
block/blk-mq.c | 139 ++++++++++++++++++++++++++++++---------------------
2 files changed, 86 insertions(+), 61 deletions(-)
Thanks
Jianchao
next reply other threads:[~2018-10-29 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 8:49 Jianchao Wang [this message]
2018-10-29 8:49 ` [PATCH V3 1/4] blk-mq: refactor the code of issue request directly Jianchao Wang
2018-10-29 8:49 ` [PATCH V3 2/4] blk-mq: insert request without involving any io scheduler Jianchao Wang
2018-10-29 8:49 ` [PATCH V3 3/4] blk-mq: issue directly with bypass_insert 'false' in blk_mq_sched_insert_requests Jianchao Wang
2018-10-29 8:49 ` [PATCH V3 4/4] blk-mq: ensure hctx to be ran on mapped cpu when issue directly Jianchao Wang
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=1540802951-5408-1-git-send-email-jianchao.w.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.