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 V6 0/5] blk-mq: refactor and fix on issue request directly Date: Tue, 13 Nov 2018 17:56:51 +0800 [thread overview] Message-ID: <1542103016-21037-1-git-send-email-jianchao.w.wang@oracle.com> (raw) Hi Jens Please consider this patchset for 4.21. It refactors the code of issue request directly to unify the interface and make the code clearer and more readable, and also fixes two defects there. The 1st patch refactors the code of issue request directly to unify the helper interface which could handle all the cases. The 2nd patch fix the issue that when queue is stopped or quiesced request may pass through bottom device's potential io scheduler. The 3rd patch fix the issue that hctx maybe ran on a cpu where it is not mapped in issue directly path. The 4th patch make blk_mq_sched_insert_requests issue requests directly with 'bypass' false, then it needn't to handle the non-issued requests any more. The 5th patch replace and kill the blk_mq_request_issue_directly. V6: - drop original 1st patch to address Jen's comment - discard the enum mq_issue_decision and blk_mq_make_decision and use BLK_STS_* return values directly to address Jen's comment. (1/5) - add 'unlikely' in blk_mq_try_issue_directly (1/5) - refactor the 2nd and 3rd patch based on the new 1st patch. - reserve the unused_cookie in 4th and 5th patch V5: - rebase against Jens' for-4.21/block branch - adjust the order of patch04 and patch05 - add patch06 to replace and kill the one line blk_mq_request_bypass_insert - comment changes V4: - split the original patch 1 into two patches, 1st and 2nd patch currently - rename the mq_decision to mq_issue_decision - comment changes 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 to refactor the code. Jianchao Wang(6) blk-mq: refactor the code of issue request directly blk-mq: fix issue directly case when q is stopped or quiesced blk-mq: ensure hctx to be ran on mapped cpu when issue directly blk-mq: issue directly with bypass 'false' in blk_mq_sched_insert_requests blk-mq: replace and kill blk_mq_request_issue_directly block/blk-core.c | 4 +- block/blk-mq-sched.c | 8 ++-- block/blk-mq.c | 126 +++++++++++++++++++++++++-------------------------- block/blk-mq.h | 7 +-- 4 files changed, 72 insertions(+), 73 deletions(-) Thanks Jianchao
next reply other threads:[~2018-11-13 9:57 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-13 9:56 Jianchao Wang [this message] 2018-11-13 9:56 ` [PATCH V6 1/5] blk-mq: refactor the code of " Jianchao Wang 2018-11-13 9:56 ` [PATCH V6 2/5] blk-mq: fix issue directly case when q is stopped or quiesced Jianchao Wang 2018-11-13 9:56 ` [PATCH V6 3/5] blk-mq: ensure hctx to be ran on mapped cpu when issue directly Jianchao Wang 2018-11-13 13:44 ` Jens Axboe 2018-11-14 2:15 ` jianchao.wang 2018-11-14 3:02 ` Ming Lei 2018-11-14 3:38 ` jianchao.wang 2018-11-13 9:56 ` [PATCH V6 4/5] blk-mq: issue directly with bypass 'false' in blk_mq_sched_insert_requests Jianchao Wang 2018-11-13 9:56 ` [PATCH V6 5/5] blk-mq: replace and kill blk_mq_request_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=1542103016-21037-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 \ --subject='Re: [PATCH V6 0/5] blk-mq: refactor and fix on issue request directly' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).