From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, Ming Lei <ming.lei@redhat.com>
Subject: [PATCH 0/5] blk-mq & dm: fix IO hang and deal with one performance issue
Date: Mon, 22 Jan 2018 11:35:45 +0800 [thread overview]
Message-ID: <20180122033550.27855-1-ming.lei@redhat.com> (raw)
Hi Jens,
This 1st patch introduces BLK_STS_DEV_RESOURCE for dealing with IO hang
when non-device resource is run out of and queue is idle, and this
approach is suggested by you.
The 2nd and 3rd patches cleans dm-rq a bit and prepares for applying
blk_get_request_notify().
The 4th patch introduces blk_get_request_notify(), still suggested by
you.
The last patch applies blk_get_request_notify() and avoids one
DM specific performance issue which is introduced by the 1st patch.
These 5 patches are against both dm(dm-4.16) and block tree(for-4.16/block).
Ming Lei (5):
blk-mq: introduce BLK_STS_DEV_RESOURCE
dm-rq: handle dispatch exception in dm_dispatch_clone_request()
dm-rq: return BLK_STS_* from map_request()
blk-mq: introduce blk_get_request_notify
dm-mpath: use blk_mq_alloc_request_notify for allocating blk-mq req
block/blk-core.c | 1 +
block/blk-mq-tag.c | 27 +++++++++++++++++++++-
block/blk-mq.c | 43 +++++++++++++++++++++++++++++------
block/blk-mq.h | 1 +
drivers/block/null_blk.c | 2 +-
drivers/block/virtio_blk.c | 2 +-
drivers/block/xen-blkfront.c | 2 +-
drivers/md/dm-mpath.c | 50 ++++++++++++++++++++++++++++++++++++++++-
drivers/md/dm-rq.c | 53 +++++++++++++++++++++++++++-----------------
drivers/md/dm.c | 1 +
drivers/scsi/scsi_lib.c | 6 ++---
include/linux/blk-mq.h | 5 +++++
include/linux/blk_types.h | 7 ++++++
13 files changed, 165 insertions(+), 35 deletions(-)
--
2.9.5
next reply other threads:[~2018-01-22 3:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 3:35 Ming Lei [this message]
2018-01-22 3:35 ` [PATCH 1/5] blk-mq: introduce BLK_STS_DEV_RESOURCE Ming Lei
2018-01-22 16:32 ` Christoph Hellwig
2018-01-22 16:49 ` Bart Van Assche
2018-01-22 16:49 ` Bart Van Assche
2018-01-23 0:57 ` Ming Lei
2018-01-23 16:17 ` Bart Van Assche
2018-01-23 16:26 ` Ming Lei
2018-01-23 16:37 ` Bart Van Assche
2018-01-23 16:41 ` Ming Lei
2018-01-23 16:47 ` Bart Van Assche
2018-01-23 16:47 ` Bart Van Assche
2018-01-23 16:49 ` Ming Lei
2018-01-23 16:54 ` Bart Van Assche
2018-01-23 16:54 ` Bart Van Assche
2018-01-23 16:59 ` Ming Lei
2018-01-23 16:59 ` Ming Lei
2018-01-23 22:01 ` Bart Van Assche
2018-01-23 22:01 ` Bart Van Assche
2018-01-24 2:31 ` Ming Lei
2018-01-22 3:35 ` [PATCH 2/5] dm-rq: handle dispatch exception in dm_dispatch_clone_request() Ming Lei
2018-01-22 3:35 ` Ming Lei
2018-01-22 3:35 ` [PATCH 3/5] dm-rq: return BLK_STS_* from map_request() Ming Lei
2018-01-22 3:35 ` Ming Lei
2018-01-22 5:35 ` Ming Lei
2018-01-22 3:35 ` [PATCH 4/5] blk-mq: introduce blk_get_request_notify Ming Lei
2018-01-22 10:19 ` Ming Lei
2018-01-22 17:13 ` Bart Van Assche
2018-01-22 17:13 ` Bart Van Assche
2018-01-23 1:29 ` Ming Lei
2018-01-22 3:35 ` [PATCH 5/5] dm-mpath: use blk_mq_alloc_request_notify for allocating blk-mq req Ming Lei
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=20180122033550.27855-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=snitzer@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.