From: Mike Snitzer <snitzer@redhat.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
dm-devel@redhat.com, linux-scsi@vger.kernel.org,
Laurence Oberman <loberman@redhat.com>,
Bart Van Assche <bart.vanassche@sandisk.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>
Subject: Re: [PATCH V3] blk-mq: introduce BLK_STS_DEV_RESOURCE
Date: Tue, 23 Jan 2018 11:20:20 -0500 [thread overview]
Message-ID: <20180123162020.GA25863@redhat.com> (raw)
In-Reply-To: <20180123161613.14214-1-ming.lei@redhat.com>
On Tue, Jan 23 2018 at 11:16am -0500,
Ming Lei <ming.lei@redhat.com> wrote:
> This status is returned from driver to block layer if device related
> resource is run out of, but driver can guarantee that IO dispatch will
> be triggered in future when the resource is available.
>
> This patch converts some drivers to use this return value. Meantime
> if driver returns BLK_STS_RESOURCE and S_SCHED_RESTART is marked, run
> queue after 10ms for avoiding IO hang.
>
> Suggested-by: Jens Axboe <axboe@kernel.dk>
> Tested-by: Laurence Oberman <loberman@redhat.com>
> Cc: Christoph Hellwig <hch@infradead.org>
> Cc: Mike Snitzer <snitzer@redhat.com>
> Cc: Laurence Oberman <loberman@redhat.com>
> Cc: Bart Van Assche <bart.vanassche@sandisk.com>
> Cc: Martin K. Petersen <martin.petersen@oracle.com>
> Cc: James E.J. Bottomley <jejb@linux.vnet.ibm.com>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
Acked-by: Mike Snitzer <snitzer@redhat.com>
Thanks Ming
next prev parent reply other threads:[~2018-01-23 16:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 16:16 [PATCH V3] blk-mq: introduce BLK_STS_DEV_RESOURCE Ming Lei
2018-01-23 16:20 ` Mike Snitzer [this message]
2018-01-23 16:24 ` Bart Van Assche
2018-01-23 16:24 ` Bart Van Assche
2018-01-23 16:37 ` Ming Lei
2018-01-23 16:57 ` Bart Van Assche
2018-01-23 16:57 ` Bart Van Assche
2018-01-24 3:31 ` Ming Lei
2018-01-27 19:09 ` Mike Snitzer
2018-01-27 22:12 ` Bart Van Assche
2018-01-27 22:12 ` Bart Van Assche
2018-01-27 23:41 ` Ming Lei
2018-01-29 16:48 ` Bart Van Assche
2018-01-29 16:48 ` Bart Van Assche
2018-01-30 1:07 ` Ming Lei
2018-01-30 1:11 ` Bart Van Assche
2018-01-30 1:11 ` Bart Van Assche
2018-01-30 3:31 ` Ming Lei
2018-01-30 3:37 ` Bart Van Assche
2018-01-30 3:37 ` Bart Van Assche
2018-01-30 3:42 ` Ming Lei
2018-01-30 3:42 ` Ming Lei
2018-01-28 0:23 ` Mike Snitzer
2018-01-28 0:54 ` Bart Van Assche
2018-01-28 0:54 ` Bart Van Assche
2018-01-28 2:03 ` Mike Snitzer
2018-01-28 3:00 ` Bart Van Assche
2018-01-28 3:00 ` Bart Van Assche
2018-01-28 4:58 ` Mike Snitzer
2018-01-28 16:57 ` Bart Van Assche
2018-01-28 16:57 ` Bart Van Assche
2018-01-28 17:26 ` Laurence Oberman
2018-01-28 11:39 ` Ming Lei
2018-01-28 17:03 ` Bart Van Assche
2018-01-28 17:03 ` Bart Van Assche
2018-01-29 2:14 ` 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=20180123162020.GA25863@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@sandisk.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=martin.petersen@oracle.com \
--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.