From: Ming Lei <tom.leiming@gmail.com>
To: Jens Axboe <axboe@fb.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Cc: Yi Zhang <yizhan@redhat.com>,
Bart Van Assche <bart.vanassche@sandisk.com>,
Ming Lei <minlei@redhat.com>
Subject: [PATCH v1 0/3] blk-mq: dying queue fix & improvement
Date: Fri, 17 Mar 2017 17:57:08 +0800 [thread overview]
Message-ID: <20170317095711.5819-1-tom.leiming@gmail.com> (raw)
From: Ming Lei <minlei@redhat.com>
Hi,
The 1st patch fixes one race between timeout and dying queue.
The 2nd patch add comments on races with timeout handler.
The 3rd patch improves handling for dying queue.
V1:
- add comments on races related with timeout handler
- add Tested-by & Reviewed-by tag
thanks,
Ming
Ming Lei (3):
blk-mq: don't complete un-started request in timeout handler
blk-mq: comment on races related timeout handler
blk-mq: start to freeze queue just after setting dying
block/blk-core.c | 7 +++++--
block/blk-mq.c | 33 +++++++++++++++++++++++----------
2 files changed, 28 insertions(+), 12 deletions(-)
--
2.9.3
next reply other threads:[~2017-03-17 9:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 9:57 Ming Lei [this message]
2017-03-17 9:57 ` [PATCH v1 1/3] blk-mq: don't complete un-started request in timeout handler Ming Lei
2017-03-18 11:24 ` Hannes Reinecke
2017-03-17 9:57 ` [PATCH v1 2/3] blk-mq: comment on races related with " Ming Lei
2017-03-17 17:39 ` Bart Van Assche
2017-03-17 18:23 ` Ming Lei
2017-03-18 11:25 ` Hannes Reinecke
2017-03-17 9:57 ` [PATCH v1 3/3] blk-mq: start to freeze queue just after setting dying Ming Lei
2017-03-17 17:32 ` Bart Van Assche
2017-03-17 18:32 ` Ming Lei
2017-03-17 20:36 ` Bart Van Assche
2017-03-17 23:26 ` Bart Van Assche
2017-03-18 1:01 ` Ming Lei
2017-03-18 11:27 ` Hannes Reinecke
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=20170317095711.5819-1-tom.leiming@gmail.com \
--to=tom.leiming@gmail.com \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minlei@redhat.com \
--cc=yizhan@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;
as well as URLs for NNTP newsgroup(s).