From: Kemeng Shi <shikemeng@huaweicloud.com>
To: hch@lst.de, axboe@kernel.dk, dwagner@suse.de, hare@suse.de,
ming.lei@redhat.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: john.garry@huawei.com, jack@suse.cz
Subject: [PATCH v4 00/14] A few bugfix and cleanup patches for blk-mq
Date: Wed, 18 Jan 2023 17:28:44 +0800 [thread overview]
Message-ID: <20230118092858.3911211-1-shikemeng@huaweicloud.com> (raw)
Hi, this series contain several bugfix patches to fix potential io
hung and a few cleanup patches to remove stale codes and unnecessary
check. Most changes are in request issue and dispatch path. Thanks.
---
V4:
-Eliminate remove of from_schedule parameter in blk_mq_commit_rqs in
patch "blk-mq: remove unncessary from_schedule parameter in" and
remove Reviewed-by tag of this changed patch.
-Trace unplug event for all commits and make patches based on new
general blk_mq_commit_rqs
-Fix some code style issues.
-Initialize ret to BLK_STS_OK in patches "blk-mq: remove unncessary
error count and commit in" and "blk-mq: use blk_mq_commit_rqs helper in
blk_mq_try_issue_list_directly".
V3:
-Collect Reviewed-by from Christoph
-Add new patch "blk-mq: make blk_mq_commit_rqs a general function for all
commits" suggested-by Christoph
-Move patch "blk-mq: remove unncessary from_schedule parameter in
blk_mq_plug_issue_direct" forwad. This is because of some abandoned
work, no influence anyway. No special attention should be paied.
-Make patch based on rewriten blk_mq_commit_rqs.
V2:
-Thanks Christoph for review and there are two fixes in v2 according
to recommends from Christoph.
1)Avoid overly long line in patch "blk-mq: avoid sleep in
blk_mq_alloc_request_hctx"
2)Check BLK_MQ_REQ_NOWAIT and BLK_MQ_REQ_RESERVED in two WARN_ON_ONCE
---
Kemeng Shi (14):
blk-mq: avoid sleep in blk_mq_alloc_request_hctx
blk-mq: remove stale comment for blk_mq_sched_mark_restart_hctx
blk-mq: wait on correct sbitmap_queue in blk_mq_mark_tag_wait
blk-mq: Fix potential io hung for shared sbitmap per tagset
blk-mq: remove unnecessary list_empty check in
blk_mq_try_issue_list_directly
blk-mq: remove unncessary from_schedule parameter in
blk_mq_plug_issue_direct
blk-mq: make blk_mq_commit_rqs a general function for all commits
blk-mq: remove unncessary error count and commit in
blk_mq_plug_issue_direct
blk-mq: use blk_mq_commit_rqs helper in blk_mq_try_issue_list_directly
blk-mq: simplify flush check in blk_mq_dispatch_rq_list
blk-mq: remove unnecessary error count and check in
blk_mq_dispatch_rq_list
blk-mq: remove set of bd->last when get driver tag for next request
fails
blk-mq: use switch/case to improve readability in
blk_mq_try_issue_list_directly
blk-mq: correct stale comment of .get_budget
block/blk-mq-sched.c | 7 +--
block/blk-mq.c | 144 +++++++++++++++++++------------------------
2 files changed, 68 insertions(+), 83 deletions(-)
--
2.30.0
reply other threads:[~2023-01-18 1:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230118092858.3911211-1-shikemeng@huaweicloud.com \
--to=shikemeng@huaweicloud.com \
--cc=axboe@kernel.dk \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=john.garry@huawei.com \
--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.