Re: [PATCH v2 4/8] blk-mq: fix blk_mq_quiesce_queue

2017-05-30 Thread Ming Lei
On Tue, May 30, 2017 at 04:54:47PM +, Bart Van Assche wrote: > On Tue, 2017-05-30 at 08:22 +0800, Ming Lei wrote: > > On Sun, May 28, 2017 at 04:10:09PM +, Bart Van Assche wrote: > > > I really would like to see the blk_queue_quiesced() tests as close as > > > possible to > > > the

Re: [PATCH v2 4/8] blk-mq: fix blk_mq_quiesce_queue

2017-05-30 Thread Bart Van Assche
On Sun, 2017-05-28 at 18:44 +0800, Ming Lei wrote: > First it is really a fix, and then a improvement, so could you tell me > where is wrong with the title and the description? Hello Ming, Can you explain me why you want to keep the blk_mq_stop_hw_queues() call in nvme_suspend_queue()? Since

Re: [PATCH v2 4/8] blk-mq: fix blk_mq_quiesce_queue

2017-05-30 Thread Bart Van Assche
On Tue, 2017-05-30 at 08:22 +0800, Ming Lei wrote: > On Sun, May 28, 2017 at 04:10:09PM +, Bart Van Assche wrote: > > I really would like to see the blk_queue_quiesced() tests as close as > > possible to > > the blk_mq_hctx_stopped() tests. But I agree that we need a way to document > >

Re: [PATCH v2 4/8] blk-mq: fix blk_mq_quiesce_queue

2017-05-29 Thread Ming Lei
On Sun, May 28, 2017 at 04:10:09PM +, Bart Van Assche wrote: > On Sun, 2017-05-28 at 18:44 +0800, Ming Lei wrote: > > On Sat, May 27, 2017 at 09:46:45PM +, Bart Van Assche wrote: > > > On Sat, 2017-05-27 at 22:21 +0800, Ming Lei wrote: > > > > bool blk_mq_can_queue(struct blk_mq_hw_ctx

Re: [PATCH v2 4/8] blk-mq: fix blk_mq_quiesce_queue

2017-05-28 Thread Bart Van Assche
On Sun, 2017-05-28 at 18:44 +0800, Ming Lei wrote: > On Sat, May 27, 2017 at 09:46:45PM +, Bart Van Assche wrote: > > On Sat, 2017-05-27 at 22:21 +0800, Ming Lei wrote: > > > bool blk_mq_can_queue(struct blk_mq_hw_ctx *hctx) > > > @@ -1108,13 +1119,15 @@ static void

Re: [PATCH v2 4/8] blk-mq: fix blk_mq_quiesce_queue

2017-05-28 Thread Ming Lei
On Sat, May 27, 2017 at 09:46:45PM +, Bart Van Assche wrote: > On Sat, 2017-05-27 at 22:21 +0800, Ming Lei wrote: > > It is required that no dispatch can happen any more once > > blk_mq_quiesce_queue() returns, and we don't have such requirement > > on APIs of stopping queue. > > > > But

Re: [PATCH v2 4/8] blk-mq: fix blk_mq_quiesce_queue

2017-05-27 Thread Bart Van Assche
On Sat, 2017-05-27 at 22:21 +0800, Ming Lei wrote: > It is required that no dispatch can happen any more once > blk_mq_quiesce_queue() returns, and we don't have such requirement > on APIs of stopping queue. > > But blk_mq_quiesce_queue() still may not block/drain dispatch in the > following

[PATCH v2 4/8] blk-mq: fix blk_mq_quiesce_queue

2017-05-27 Thread Ming Lei
It is required that no dispatch can happen any more once blk_mq_quiesce_queue() returns, and we don't have such requirement on APIs of stopping queue. But blk_mq_quiesce_queue() still may not block/drain dispatch in the following cases: - direct issue or BLK_MQ_S_START_ON_RUN - in theory, new