From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
Dongli Zhang <dongli.zhang@oracle.com>,
Hannes Reinecke <hare@suse.de>, Daniel Wagner <dwagner@suse.de>,
Christoph Hellwig <hch@lst.de>,
John Garry <john.garry@huawei.com>
Subject: [PATCH 0/2] blk-mq: fix handling cpu hotplug
Date: Fri, 5 Jun 2020 19:44:08 +0800 [thread overview]
Message-ID: <20200605114410.2416726-1-ming.lei@redhat.com> (raw)
Hi Jens,
The 1st patch avoids to fail driver tag allocation because of inactive
hctx, so hang risk can be killed during cpu hotplug.
The 2nd patch fixes blk_mq_all_tag_iter so that we can drain all
requests before one hctx becomes inactive.
Both fixes bf0beec0607d ("blk-mq: drain I/O when all CPUs in a hctx are
offline").
John has verified that the two can fix his request timeout issue during
cpu hotplug.
Christoph Hellwig (1):
blk-mq: split out a __blk_mq_get_driver_tag helper
Ming Lei (1):
blk-mq: fix blk_mq_all_tag_iter
block/blk-mq-tag.c | 39 ++++++++++++++++++++++++++++++++++++---
block/blk-mq-tag.h | 8 ++++++++
block/blk-mq.c | 29 -----------------------------
block/blk-mq.h | 1 -
4 files changed, 44 insertions(+), 33 deletions(-)
Cc: Dongli Zhang <dongli.zhang@oracle.com>
Cc: Hannes Reinecke <hare@suse.de>
Cc: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@lst.de>
Cc: John Garry <john.garry@huawei.com>
--
2.25.2
next reply other threads:[~2020-06-05 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 11:44 Ming Lei [this message]
2020-06-05 11:44 ` [PATCH 1/2] blk-mq: split out a __blk_mq_get_driver_tag helper Ming Lei
2020-06-05 11:44 ` [PATCH 2/2] blk-mq: fix blk_mq_all_tag_iter Ming Lei
2020-06-05 11:49 ` [PATCH 0/2] blk-mq: fix handling cpu hotplug John Garry
2020-06-05 16:08 ` John Garry
2020-06-07 14:57 ` 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=20200605114410.2416726-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=dongli.zhang@oracle.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=john.garry@huawei.com \
--cc=linux-block@vger.kernel.org \
/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.