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 V2 0/3] blk-mq: refactor and fix on issue request directly
Date: Sat, 27 Oct 2018 00:01:08 +0800 [thread overview]
Message-ID: <1540569671-6589-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 blk_mq_try_issue_directly handle return value of .queue_rq itself.
The 2nd patch make blk_mq_sched_insert_requests issue request directly with
bypass "false" instead of the "true", then needn't to handle the non-issued
requests any more.
The 3rd patch ensures the hctx to be ran on its mapped cpu in issue directly
path.
V2:
- Add 1st and 2nd patch.
Jianchao Wang(3)
blk-mq: refactor the code of issue request directly
blk-mq: issue directly with bypass 'false' in blk_mq_sched_insert_requests
blk-mq: ensure hctx to be ran on mapped cpu when issue
block/blk-mq-sched.c | 8 ++--
block/blk-mq.c | 128 ++++++++++++++++++++++++---------------------------
2 files changed, 63 insertions(+), 73 deletions(-)
next reply other threads:[~2018-10-26 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 16:01 Jianchao Wang [this message]
2018-10-26 16:01 ` [PATCH V2 1/3] blk-mq: refactor the code of " Jianchao Wang
2018-10-29 2:49 ` Ming Lei
2018-10-29 5:40 ` jianchao.wang
2018-10-26 16:01 ` [PATCH V2 2/3] blk-mq: issue directly with bypass 'false' in blk_mq_sched_insert_requests Jianchao Wang
2018-10-26 16:01 ` [PATCH V2 3/3] 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=1540569671-6589-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 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®